Re: [PATCH] Stop automatic dependency selection on setup.exe chooser screen
On 7 August 2010 18:14, Christopher Faylor wrote: On Sat, Aug 07, 2010 at 10:56:48AM +0200, Corinna Vinschen wrote: Please go ahead and check it in, after testing. What's this after testing thing? Oh. Wait. Nevermind. Good idea. I've tortured it a fair bit, including trying to delete random packages, setting Keep, Prev, and Exp, and selecting all packages (whereby the resolver finds a bunch of obsolete packages that still need to be added). I didn't see anything untoward, but of course that's no guarantee for anything. We could really do with some sort of beta testing scheme for setup.exe. Still, I'm confident 2.711 is better than 2.708. The main concern I have about the dependency checking now is the amount of time it takes. On my netbook, it's about a minute with all packages selected, so that's pretty much the worst case. I think this is due to packagedb::findBinary, which is called for every dependency, doing a linear search through all packages. I suspect a precomputed map could make quite a difference there. Andy
Re: [PATCH] Stop automatic dependency selection on setup.exe chooser screen
On Aug 7 12:21, Andy Koppe wrote: On 7 August 2010 10:20, Corinna Vinschen wrote: Maybe it's better to provide as much information as possible. What about this: libao (1.0.0-1) Cross-Platform Audio Output Library (Transition) Required by: libao4, libao-devel libao-devel (1.0.0-1) Cross-Platform Audio Output Library (Development) Required by: libao libao4 (1.0.0-1) Cross-Platform Audio Output Library (Runtime) Required by: vorbis-tools, libao, libao-devel [...] This looks good, I agree it's worth providing all that info. I checked this in. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
gcc4-core PACKAGE BUG
Hi Dave, testing with the latest setup.exe I came across an error message in postinstall: gcc4-core.sh, exit code 126 Manuall testing turned up that the script /usr/sbin/fix-libtool-scripts-for-latest-gcc-runtimes.sh is not executable. Either /etc/postinstall/gcc4-core.sh should call the script like this: sh /usr/sbin/fix-libtool-scripts-for-latest-gcc-runtimes.sh or the script should be executable. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: ITP: rtorret, libtorrent, libsigc++
On 2010/08/07 8:30 PM, Chris Sutcliffe wrote: Hi Chuck, Thank you for your thorough review of the packaging and the associated patches. I've decided for ligsigc++ and libtorrent to make the base packages the license packages as opposed to having '-lic' packages. I've made all the changes you recommended and included Corinna's updated d_reclen change. I have uploaded all new versions of the packages: libsigc++-2.0-2.2.8-1: wget -x -nH --cut-dirs=1 \ http://emergedesktop.org/cygwin/libsigc++/setup.hint \ http://emergedesktop.org/cygwin/libsigc++/libsigc++2.0-2.2.8-1-src.tar.bz2 \ http://emergedesktop.org/cygwin/libsigc++/libsigc++2.0-2.2.8-1.tar.bz2 \ http://emergedesktop.org/cygwin/libsigc++/libsigc++2.0_0/setup.hint \ http://emergedesktop.org/cygwin/libsigc++/libsigc++2.0_0/libsigc++2.0_0-2.2.8-1.tar.bz2 \ http://emergedesktop.org/cygwin/libsigc++/libsigc++2.0-devel/setup.hint \ http://emergedesktop.org/cygwin/libsigc++/libsigc++2.0-devel/libsigc++2.0-devel-2.2.8-1.tar.bz2 \ http://emergedesktop.org/cygwin/libsigc++/libsigc++2.0-doc/setup.hint \ http://emergedesktop.org/cygwin/libsigc++/libsigc++2.0-doc/libsigc++2.0-doc-2.2.8-1.tar.bz2 libtorrent-0.12.6-1: wget -x -nH --cut-dirs=1 \ http://emergedesktop.org/cygwin/libtorrent/setup.hint \ http://emergedesktop.org/cygwin/libtorrent/libtorrent-0.12.6-1-src.tar.bz2 \ http://emergedesktop.org/cygwin/libtorrent/libtorrent-0.12.6-1.tar.bz2 \ http://emergedesktop.org/cygwin/libtorrent/libtorrent11/setup.hint \ http://emergedesktop.org/cygwin/libtorrent/libtorrent11/libtorrent11-0.12.6-1.tar.bz2 \ http://emergedesktop.org/cygwin/libtorrent/libtorrent-devel/setup.hint \ http://emergedesktop.org/cygwin/libtorrent/libtorrent-devel/libtorrent-devel-0.12.6-1.tar.bz2 rtorrent-0.8.6-1: wget -x -nH --cut-dirs=1 \ http://emergedesktop.org/cygwin/rtorrent/setup.hint \ http://emergedesktop.org/cygwin/rtorrent/rtorrent-0.8.6-1-src.tar.bz2 \ http://emergedesktop.org/cygwin/rtorrent/rtorrent-0.8.6-1.tar.bz2 My preliminary testing of the rtorrent client has been positive. Everything seems to be working as expected so far. Excellent! Some notes about the packaging: The setup.hints of the libtorrent subpackages (libtorrent11 and libtorrent-devel) are missing their 'external-source: libtorrent' line. The setup.hint of libtorrent11 is missing 'libsigc++2.0_0' from its 'requires:' line (likely a typo, missing the trailing _0). The setup.hint of libsigc++2.0_0 is missing 'libgcc1' and 'libstdc++6' from its 'requires:' line. The setup.hint of rtorrent is missing 'libgcc1' and 'libsigc++2.0_0' from its 'requires:' line (the latter is, again, likely a typo). The setup.hints of the libsigc++2.0 subpackages are missing 'libsigc++2.0' from their 'requires:' lines. The setup.hints of the libtorrent subpackages are missing 'libtorrent' from their 'requires:' lines. Best regards, -SM --
build-docbook-catalog PACKAGE BUG
Hi Yaakov, I just encountered a problem with the postinstall scripts of docbook-xml42 and docbook-xsl, an exit code of 1. Both postinstall scripts depend on the /usr/bin/build-docbook-catalog script which in turn calls xmlcatalog --noout --create /etc/xml/catalog The problem here is that xmlcatalog fails if the parent directory, here /etc/xml, does not exist. However, the build-docbook-catalog does neither check the existence of the /etc/xml dir, nor does it make any attempt to mkdir it. As soo as I mkdir the /etc/xml directory, the docbook-xml42.sh and docbook-xsl.sh postinstall scripts work as expected. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: ITP: rtorret, libtorrent, libsigc++
On 8/8/2010 12:59 PM, Steven Monai wrote: Some notes about the packaging: The setup.hints of the libtorrent subpackages (libtorrent11 and libtorrent-devel) are missing their 'external-source: libtorrent' line. Odd...my local (modified) copy has these; I wonder if the patch I posted for Chris somehow missed this change. In any case, Steven is right and the most recent version of these files are missing the external-source line. The setup.hint of libtorrent11 is missing 'libsigc++2.0_0' from its 'requires:' line (likely a typo, missing the trailing _0). My fault: my local modified copy also has this typo. Also, I think libtorrent11 should list libgcc1 as a requirement, in addition to libstdc++6, since cygtorrent-11.dll has a direct dependence on both libraries (in addition to the others already listed). Also, the libtorrent Cygwin README claims that various docu is in the development package, but it is not. It's in the main package. The setup.hints of the libtorrent subpackages are missing 'libtorrent' from their 'requires:' lines. Well, yes, they are missing that requirement. But that's because libtorrent is NOT a requirement for libtorrent11 nor libtorrent-devel. It only provides some text documentation; why should those other packages require it? The setup.hint of libsigc++2.0_0 is missing 'libgcc1' and 'libstdc++6' from its 'requires:' line. My fault, again. I thought I fixed that, but my locally modified copy does NOT actually contain these requirements; if Chris took my updates directly, well... This also means that the libsigc++2.0 Cygwin README is missing the following runtime requirements: libgcc1-4.3.4-3 libstdc++6-4.3.4-3 The setup.hints of the libsigc++2.0 subpackages are missing 'libsigc++2.0' from their 'requires:' lines. Again, the libsigc++2.0 package provides nothing but documentation. Why should those subpackages require it? The setup.hint of rtorrent is missing 'libgcc1' and 'libsigc++2.0_0' from its 'requires:' line (the latter is, again, likely a typo). Steven is correct here, too. The typo is in my (locally modified) copy, too -- so blame me for that one. However, my locally modified copy has libgcc1 so I'm not sure how it went missing. Furthermore, the rtorrent Cygwin README needs a similar update (libsigc++2.0 - libsigc++2.0_0) under its runtime requirements list. Also, that README is missing the following runtime requirements: libncursesw10 libgcc1 It's also missing the following build requirements: libsigc++2.0-devel libstdc++-devel (*) (*) all three Cygwin READMEs are probably missing this one; I thought it came with the gcc4-g++ package but apparently not. All three READMEs should probably list gcc4-g++ as a build requirement as well (we often elide the obvious build requirements like gcc, binutils, make, and bash -- and cygport/patch/tar/gz/bz2/xz, but the need for a C++ compiler should probably be spelled out explicitly in the README). -- Chuck
Re: ITP: rtorret, libtorrent, libsigc++
On 8 August 2010 14:48, Charles Wilson wrote: On 8/8/2010 12:59 PM, Steven Monai wrote: Some notes about the packaging: The setup.hints of the libtorrent subpackages (libtorrent11 and libtorrent-devel) are missing their 'external-source: libtorrent' line. Odd...my local (modified) copy has these; I wonder if the patch I posted for Chris somehow missed this change. In any case, Steven is right and the most recent version of these files are missing the external-source line. My bad, I didn't use your patches directly, I cut-and-paste the relevant parts and apparently missed a few things. Also, the libtorrent Cygwin README claims that various docu is in the development package, but it is not. It's in the main package. Erm... it actually should say: Files included in the licensing package: usr/share/doc/libtorrent/AUTHORS usr/share/doc/libtorrent/COPYING usr/share/doc/libtorrent/NEWS usr/share/doc/libtorrent/README where the 'licensing' package is the 'main' package. I've hopefully captured all the recommended changes and I'm hoping the third time is the charm: libsigc++-2.0-2.2.8-1: wget -x -nH --cut-dirs=1 \ http://emergedesktop.org/cygwin/libsigc++/setup.hint \ http://emergedesktop.org/cygwin/libsigc++/libsigc++2.0-2.2.8-1-src.tar.bz2 \ http://emergedesktop.org/cygwin/libsigc++/libsigc++2.0-2.2.8-1.tar.bz2 \ http://emergedesktop.org/cygwin/libsigc++/libsigc++2.0_0/setup.hint \ http://emergedesktop.org/cygwin/libsigc++/libsigc++2.0_0/libsigc++2.0_0-2.2.8-1.tar.bz2 \ http://emergedesktop.org/cygwin/libsigc++/libsigc++2.0-devel/setup.hint \ http://emergedesktop.org/cygwin/libsigc++/libsigc++2.0-devel/libsigc++2.0-devel-2.2.8-1.tar.bz2 \ http://emergedesktop.org/cygwin/libsigc++/libsigc++2.0-doc/setup.hint \ http://emergedesktop.org/cygwin/libsigc++/libsigc++2.0-doc/libsigc++2.0-doc-2.2.8-1.tar.bz2 libtorrent-0.12.6-1: wget -x -nH --cut-dirs=1 \ http://emergedesktop.org/cygwin/libtorrent/setup.hint \ http://emergedesktop.org/cygwin/libtorrent/libtorrent-0.12.6-1-src.tar.bz2 \ http://emergedesktop.org/cygwin/libtorrent/libtorrent-0.12.6-1.tar.bz2 \ http://emergedesktop.org/cygwin/libtorrent/libtorrent11/setup.hint \ http://emergedesktop.org/cygwin/libtorrent/libtorrent11/libtorrent11-0.12.6-1.tar.bz2 \ http://emergedesktop.org/cygwin/libtorrent/libtorrent-devel/setup.hint \ http://emergedesktop.org/cygwin/libtorrent/libtorrent-devel/libtorrent-devel-0.12.6-1.tar.bz2 rtorrent-0.8.6-1: wget -x -nH --cut-dirs=1 \ http://emergedesktop.org/cygwin/rtorrent/setup.hint \ http://emergedesktop.org/cygwin/rtorrent/rtorrent-0.8.6-1-src.tar.bz2 \ http://emergedesktop.org/cygwin/rtorrent/rtorrent-0.8.6-1.tar.bz2 Cheers! Chris -- Chris Sutcliffe http://emergedesktop.org http://www.google.com/profiles/ir0nh34d
Re: ITP: rtorret, libtorrent, libsigc++
On 2010/08/08 11:48 AM, Charles Wilson wrote: On 8/8/2010 12:59 PM, Steven Monai wrote: Some notes about the packaging: The setup.hints of the libtorrent subpackages are missing 'libtorrent' from their 'requires:' lines. Well, yes, they are missing that requirement. But that's because libtorrent is NOT a requirement for libtorrent11 nor libtorrent-devel. It only provides some text documentation; why should those other packages require it? Practically speaking, yes, it is true that the subpackages don't really require the text docs provided by the libtorrent package to correctly perform their function. However, the entire raison d'etre for the libtorrent package seems to be to provide the text docs that upstream intends to accompany the library. So personally, I would make all of libtorrent's subpackages require libtorrent, so that the upstream text docs (including the COPYING file, which contains the GPL license notice) are always installed when any of the subpackages are installed. It is ultimately the packager's decision about how best to distribute the GPL notice with the software. In this case, making the subpackages require the libtorrent package would be an easy way to accomplish that, but it's certainly not the only way. It's really up to Chris to decide. The setup.hints of the libsigc++2.0 subpackages are missing 'libsigc++2.0' from their 'requires:' lines. Again, the libsigc++2.0 package provides nothing but documentation. Why should those subpackages require it? See above, s/libtorrent/libsigc++2.0/ -SM --
Re: ITP: rtorret, libtorrent, libsigc++
On 8 August 2010 16:40, Steven Monai wrote: Practically speaking, yes, it is true that the subpackages don't really require the text docs provided by the libtorrent package to correctly perform their function. However, the entire raison d'etre for the libtorrent package seems to be to provide the text docs that upstream intends to accompany the library. So personally, I would make all of libtorrent's subpackages require libtorrent, so that the upstream text docs (including the COPYING file, which contains the GPL license notice) are always installed when any of the subpackages are installed. It is ultimately the packager's decision about how best to distribute the GPL notice with the software. In this case, making the subpackages require the libtorrent package would be an easy way to accomplish that, but it's certainly not the only way. It's really up to Chris to decide. Valid point. I'll change the hint files for libtorrent and libsigc++ and upload new versions shortly. Cheers! Chris -- Chris Sutcliffe http://emergedesktop.org http://www.google.com/profiles/ir0nh34d
Re: ITP: rtorret, libtorrent, libsigc++
On 8 August 2010 16:45, Chris Sutcliffe wrote: Valid point. I'll change the hint files for libtorrent and libsigc++ and upload new versions shortly. Done: libsigc++-2.0-2.2.8-1: wget -x -nH --cut-dirs=1 \ http://emergedesktop.org/cygwin/libsigc++/setup.hint \ http://emergedesktop.org/cygwin/libsigc++/libsigc++2.0-2.2.8-1-src.tar.bz2 \ http://emergedesktop.org/cygwin/libsigc++/libsigc++2.0-2.2.8-1.tar.bz2 \ http://emergedesktop.org/cygwin/libsigc++/libsigc++2.0_0/setup.hint \ http://emergedesktop.org/cygwin/libsigc++/libsigc++2.0_0/libsigc++2.0_0-2.2.8-1.tar.bz2 \ http://emergedesktop.org/cygwin/libsigc++/libsigc++2.0-devel/setup.hint \ http://emergedesktop.org/cygwin/libsigc++/libsigc++2.0-devel/libsigc++2.0-devel-2.2.8-1.tar.bz2 \ http://emergedesktop.org/cygwin/libsigc++/libsigc++2.0-doc/setup.hint \ http://emergedesktop.org/cygwin/libsigc++/libsigc++2.0-doc/libsigc++2.0-doc-2.2.8-1.tar.bz2 libtorrent-0.12.6-1: wget -x -nH --cut-dirs=1 \ http://emergedesktop.org/cygwin/libtorrent/setup.hint \ http://emergedesktop.org/cygwin/libtorrent/libtorrent-0.12.6-1-src.tar.bz2 \ http://emergedesktop.org/cygwin/libtorrent/libtorrent-0.12.6-1.tar.bz2 \ http://emergedesktop.org/cygwin/libtorrent/libtorrent11/setup.hint \ http://emergedesktop.org/cygwin/libtorrent/libtorrent11/libtorrent11-0.12.6-1.tar.bz2 \ http://emergedesktop.org/cygwin/libtorrent/libtorrent-devel/setup.hint \ http://emergedesktop.org/cygwin/libtorrent/libtorrent-devel/libtorrent-devel-0.12.6-1.tar.bz2 rtorrent-0.8.6-1: wget -x -nH --cut-dirs=1 \ http://emergedesktop.org/cygwin/rtorrent/setup.hint \ http://emergedesktop.org/cygwin/rtorrent/rtorrent-0.8.6-1-src.tar.bz2 \ http://emergedesktop.org/cygwin/rtorrent/rtorrent-0.8.6-1.tar.bz2 Cheers! Chris -- Chris Sutcliffe http://emergedesktop.org http://www.google.com/profiles/ir0nh34d
[ITP] gnucap - initial questions
The Gnu Circuit Analysis Package has a stable version 0.35 from 2006 and a very usable dev version from December 2009. I have found it useful in my work, and considerably easier than trying to compile SPICE or find a decent free SPICE binary. There are already Debian and Fedora packages. It compiles in Cygwin with an extremely simple 5 line patch, which has not changed over multiple releases from the 2006 version to today. Is there interest in making it a Cygwin package? I'm willing to put together a current package, but I'm not confident that I can handle porting future releases if they require more complicated patching. Perhaps someone else would be willing to take this up? I would lean towards making the initial package the latest dev version and the previous version the stable 0.35 release; what is standard practice? Best, Peter
Re: [ITP] gnucap - initial questions
On Sun, 2010-08-08 at 20:10 -0700, Peter Li wrote: The Gnu Circuit Analysis Package has a stable version 0.35 from 2006 and a very usable dev version from December 2009. I have found it useful in my work, and considerably easier than trying to compile SPICE or find a decent free SPICE binary. There are already Debian and Fedora packages. It compiles in Cygwin with an extremely simple 5 line patch, which has not changed over multiple releases from the 2006 version to today. I did not need a patch to build gnucap; I just added -DRTLD_LOCAL=0 (ahem!) to CPPFLAGS. Did you need something besides that? Is there interest in making it a Cygwin package? I'm willing to put together a current package, but I'm not confident that I can handle porting future releases if they require more complicated patching. Perhaps someone else would be willing to take this up? If it hasn't needed extensive patching for such a long time, I doubt it would in the future. If you want to maintain this within the distro, please feel free to borrow from Ports: http://cygwin-ports.git.sourceforge.net/git/gitweb.cgi?p=cygwin-ports/ports;a=tree;f=science/gnucap This isn't the latest devel version, but should be plenty to get you started. I would lean towards making the initial package the latest dev version and the previous version the stable 0.35 release; what is standard practice? The main distros seem to stick with 0.35, so perhaps you want to make 0.35 curr: and the latest dev as test:, if you feel a need to support both. Yaakov
