public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
* [ITA] libsigc2.0, [ITP] libsigc3.0
@ 2020-05-14 21:14 Ken Brown
  2020-05-15  1:51 ` Marco Atzeri
  2020-05-15  5:19 ` Yaakov Selkowitz
  0 siblings, 2 replies; 5+ messages in thread
From: Ken Brown @ 2020-05-14 21:14 UTC (permalink / raw)
  To: cygwin-apps

[-- Attachment #1: Type: text/plain, Size: 281 bytes --]

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.

Ken

[-- Attachment #2: libsigc2.0.cygport --]
[-- Type: text/plain, Size: 714 bytes --]

ORIG_PN="libsigc++"
inherit gtkmm

NAME="libsigc2.0"
VERSION=2.10.3
RELEASE=1
CATEGORY="Libs"
SUMMARY="C++ typesafe callback library"
DESCRIPTION="libsigc++ implements a typesafe callback system for standard C++.
It allows you to define signals and to connect those signals to any callback
function, either global or a member function, regardless of whether it is
static or virtual."
HOMEPAGE="https://libsigcplusplus.github.io/libsigcplusplus/"

PKG_NAMES="${NAME}_0 ${NAME}-devel ${NAME}-doc"
libsigc2_0_0_CONTENTS="usr/bin/*-2.0-0.dll usr/share/doc/${NAME}/"
libsigc2_0_devel_CONTENTS='usr/include/ usr/lib/'
libsigc2_0_doc_CONTENTS='usr/share/devhelp/ usr/share/doc/libsigc++-2.0/'

BUILD_REQUIRES="mm-common"

[-- Attachment #3: libsigc3.0.cygport --]
[-- Type: text/plain, Size: 713 bytes --]

ORIG_PN="libsigc++"
inherit gtkmm

NAME="libsigc3.0"
VERSION=3.0.3
RELEASE=1
CATEGORY="Libs"
SUMMARY="C++ typesafe callback library"
DESCRIPTION="libsigc++ implements a typesafe callback system for standard C++.
It allows you to define signals and to connect those signals to any callback
function, either global or a member function, regardless of whether it is
static or virtual."
HOMEPAGE="https://libsigcplusplus.github.io/libsigcplusplus/"

PKG_NAMES="${NAME}_0 ${NAME}-devel ${NAME}-doc"
libsigc3_0_0_CONTENTS="usr/bin/*-3.0-0.dll usr/share/doc/${NAME}/"
libsigc3_0_devel_CONTENTS='usr/include/ usr/lib/'
libsigc3_0_doc_CONTENTS='usr/share/devhelp/ usr/share/doc/libsigc++-3.0/'

BUILD_REQUIRES="mm-common"

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [ITA] libsigc2.0, [ITP] libsigc3.0
  2020-05-14 21:14 [ITA] libsigc2.0, [ITP] libsigc3.0 Ken Brown
@ 2020-05-15  1:51 ` Marco Atzeri
  2020-05-15  5:19 ` Yaakov Selkowitz
  1 sibling, 0 replies; 5+ messages in thread
From: Marco Atzeri @ 2020-05-15  1:51 UTC (permalink / raw)
  To: cygwin-apps

Am 14.05.2020 um 23:14 schrieb Ken Brown via Cygwin-apps:
> 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.
> 
> Ken

changed maintainer and added 3.0

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [ITA] libsigc2.0, [ITP] libsigc3.0
  2020-05-14 21:14 [ITA] libsigc2.0, [ITP] libsigc3.0 Ken Brown
  2020-05-15  1:51 ` Marco Atzeri
@ 2020-05-15  5:19 ` Yaakov Selkowitz
  2020-05-15 11:40   ` Ken Brown
  1 sibling, 1 reply; 5+ messages in thread
From: Yaakov Selkowitz @ 2020-05-15  5:19 UTC (permalink / raw)
  To: cygwin-apps

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?

--
Yaakov



^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [ITA] libsigc2.0, [ITP] libsigc3.0
  2020-05-15  5:19 ` Yaakov Selkowitz
@ 2020-05-15 11:40   ` Ken Brown
  2020-05-22 19:05     ` Ken Brown
  0 siblings, 1 reply; 5+ messages in thread
From: Ken Brown @ 2020-05-15 11:40 UTC (permalink / raw)
  To: cygwin-apps

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.

Ken

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [ITA] libsigc2.0, [ITP] libsigc3.0
  2020-05-15 11:40   ` Ken Brown
@ 2020-05-22 19:05     ` Ken Brown
  0 siblings, 0 replies; 5+ messages in thread
From: Ken Brown @ 2020-05-22 19:05 UTC (permalink / raw)
  To: cygwin-apps

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2020-05-22 19:05 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-05-14 21:14 [ITA] libsigc2.0, [ITP] libsigc3.0 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 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).