From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps <cygwin-apps@cygwin.com>
Subject: Re: [ITA] libsigc2.0, [ITP] libsigc3.0
Date: Fri, 22 May 2020 15:05:47 -0400 [thread overview]
Message-ID: <655abd70-54b6-68c2-241c-54e0f78ac015@cornell.edu> (raw)
In-Reply-To: <e9aefc45-10b9-fecd-7693-72b5ff0e0d50@cornell.edu>
On 5/15/2020 7:40 AM, Ken Brown via Cygwin-apps wrote:
> On 5/15/2020 1:19 AM, Yaakov Selkowitz wrote:
>> On Thu, 2020-05-14 at 17:14 -0400, Ken Brown via Cygwin-apps wrote:
>>> cygport files attached. I've updated libsigc2.0 to the latest release in the
>>> 2.0 series, and I've created libsigc3.0 as a new package, as Fedora does. Note:
>>> If you want to do a test build of the latter, you'll need to install the updated
>>> mm-common from the previous ITA.
>>
>> These look fine. Just curious, were you planning on doing the entire
>> (or some part of) GTKmm stack?
>
> I don't really have a plan at the moment. I started off with the idea of
> adopting all of your library packages that are needed by TeX Live. But then I
> started finding packages whose latest versions wouldn't build unless other
> packages were updated, so I adopted those too.
>
> I'm almost done with this limited project, and then I'll take a look to see what
> else makes sense.
Things are clearer now. Initially I adopted Cairo because it's needed by TeX
Live. Then I saw a cairomm1.0 package and thought I should it adopt it along
with Cairo. This led to libsigc++. Now that I understand that these are part
of a bigger GTKmm project, I'm not interested in going further. I'll keep the
ones I've already adopted unless someone else wants them, in which case I'll
gladly give them up.
Ken
prev parent reply other threads:[~2020-05-22 19:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 21:14 Ken Brown
2020-05-15 1:51 ` Marco Atzeri
2020-05-15 5:19 ` Yaakov Selkowitz
2020-05-15 11:40 ` Ken Brown
2020-05-22 19:05 ` Ken Brown [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=655abd70-54b6-68c2-241c-54e0f78ac015@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).