cygport: check setup.hint?
When I build a package using cygport, I sometimes forget to run cygport's dep command to make sure my setup.hint is up to date. I think it would be useful for cygport to do this as part of its packaging step. It could print out a list of dependencies or, better, print a warning if there are dependencies that are not listed in any of the setup.hint files. Ken
Re: [ITP] mosh with protobuf and perl-IO-Tty
On Tue, Jul 17, 2012 at 9:57 PM, Yaakov (Cygwin/X) wrote: On 2012-07-17 18:00, Reini Urban wrote: mosh-1.2.2-1 protobuf-2.4.1-1 perl-IO-Tty-1.10-1 hints and packages here: http://perl514.cpanel.net/cygwin/ I'm getting connection timeout errors. I got firewalled somehow. Sorry. I put it now here: http://rurban.xarch.at/software/cygwin/release/perl-IO-Tty/ http://rurban.xarch.at/software/cygwin/release/mosh/ http://rurban.xarch.at/software/cygwin/release/protobuf/ -- Reini Urban http://cpanel.net/ http://www.perl-compiler.org/
Re: [ITA] dejagnu
On Tue, Jul 17, 2012 at 10:23:30PM -0500, Yaakov (Cygwin/X) wrote: It slipped by me at the time[1], but cgf asked if I could update dejagnu, so here it is: ftp://ftp.cygwinports.org/pub/cygwinports/release-2/dejagnu/ Yaakov [1] http://cygwin.com/ml/cygwin/2012-04/msg00649.html This YA raises the question of What the #(* is going on with byacc I just uploaded another version and will send out another announcement. I'm obviously doing something strange to keep the old 2001 version alive while nuking new versions but I don't know quite what that is.
Re: Python 3.2 cygport script
Yaakov, On Fri, Jul 06, 2012 at 08:47:47AM -0500, Yaakov (Cygwin/X) wrote: On 2012-06-26 02:51, Yaakov (Cygwin/X) wrote: On Fri, 2012-06-22 at 13:18 -0400, Jason Tishler wrote: I really appreciate your feedback. Can you post your WIP Python 3.2 cygport script and patches? http://cygwin-ports.git.sourceforge.net/git/gitweb.cgi?p=cygwin-ports/python3 http://cygwin-ports.git.sourceforge.net/git/gitweb.cgi?p=cygwin-ports/python3-doc I just pushed an additional patch to fix ctypes for 3.2. Thanks for the above. BTW, to get the _dbm module to build I had to change 3.1-dbm.patch as follows: @@ -1077,6 +1077,8 @@ if self.compiler.find_library_file(lib_dirs, 'ndbm'): ndbm_libs = ['ndbm'] +elif self.compiler.find_library_file(lib_dirs, 'gdbm_compat'): +ndbm_libs = ['gdbm_compat'] else: ndbm_libs = [] print(building dbm using ndbm) Additionally, I removed --with-dbmliborder=gdbm from CYGCONF_ARGS. Note that the above changes make the 3.2 _dbm build more like the 2.6 one. Did the _dbm module build for you with your python3-3.2.3-1.cygport script? It didn't when I tried it. Is the above approach OK? Or, can you think of a better way? Thanks, Jason
Re: [ITP] mosh with protobuf and perl-IO-Tty
On 2012-07-18 09:07, Reini Urban wrote: http://rurban.xarch.at/software/cygwin/release/perl-IO-Tty/ http://rurban.xarch.at/software/cygwin/release/mosh/ http://rurban.xarch.at/software/cygwin/release/protobuf/ GTG; I'll remove protobuf from Ports. Yaakov
Re: [ITP][RFU][1.3.4] pv
On 17/07/2012 0:56, Yaakov (Cygwin/X) wrote: On 2012-07-16 06:10, Aaron Schneider wrote: wget http://pvcyg.awardspace.biz/setup.hint wget http://pvcyg.awardspace.biz/pv-1.3.4-1.tar.bz2 wget http://pvcyg.awardspace.biz/pv-1.3.4-1-src.tar.bz2 This is missing NLS support. Please install gettext and rebuild, then fix the requires accordingly (and 'cygwin' should not be listed). Yaakov Solved. The changes are: * Some minor edition in README (deleted cygwin from runtime requirements, updated list of included files) * CYGCONF_ARGS= --enable-nls --enable-lfs --disable-debugging * No 'requires' at setup.hint wget http://pvcyg.awardspace.biz/2/setup.hint wget http://pvcyg.awardspace.biz/2/pv-1.3.4-1.tar.bz2 wget http://pvcyg.awardspace.biz/2/pv-1.3.4-1-src.tar.bz2
Re: [ITP][RFU][1.3.4] pv
On 2012-07-18 18:27, Aaron Schneider wrote: Solved. The changes are: * Some minor edition in README (deleted cygwin from runtime requirements, updated list of included files) You can list cygwin as a dep in the README, just not in the setup.hint. * CYGCONF_ARGS= --enable-nls --enable-lfs --disable-debugging * No 'requires' at setup.hint If you enabled NLS then there requires: cannot be empty. Yaakov
Re: [ITP][RFU][1.3.4] pv
On 19/07/2012 1:49, Yaakov (Cygwin/X) wrote: On 2012-07-18 18:27, Aaron Schneider wrote: Solved. The changes are: * Some minor edition in README (deleted cygwin from runtime requirements, updated list of included files) You can list cygwin as a dep in the README, just not in the setup.hint. * CYGCONF_ARGS= --enable-nls --enable-lfs --disable-debugging * No 'requires' at setup.hint If you enabled NLS then there requires: cannot be empty. Yaakov Changed. * requires: libintl8 libiconv2 wget http://pvcyg.awardspace.biz/3/setup.hint wget http://pvcyg.awardspace.biz/3/pv-1.3.4-1.tar.bz2 wget http://pvcyg.awardspace.biz/3/pv-1.3.4-1-src.tar.bz2
Re: [ITP][RFU][1.3.4] pv
On 2012-07-18 19:36, Aaron Schneider wrote: * requires: libintl8 libiconv2 Close; you only need libintl8. The binary isn't linked against libiconv2; that only shows up because libintl8 depends on it. Instead of relying on cygcheck or ldd to determine dependencies, you should use cygport itself, IOW: cygport pv-1.3.4-1.cygport deps wget http://pvcyg.awardspace.biz/3/setup.hint wget http://pvcyg.awardspace.biz/3/pv-1.3.4-1.tar.bz2 wget http://pvcyg.awardspace.biz/3/pv-1.3.4-1-src.tar.bz2 Otherwise this looks GTG, so I fixed the setup.hint accordingly and uploaded this. Please announce. Yaakov
Re: cygport: check setup.hint?
On 2012-07-18 06:53, Ken Brown wrote: When I build a package using cygport, I sometimes forget to run cygport's dep command to make sure my setup.hint is up to date. I think it would be useful for cygport to do this as part of its packaging step. It could print out a list of dependencies or, better, print a warning if there are dependencies that are not listed in any of the setup.hint files. I'm actually working on setup.hint generation in cygport, which would work by defining [PKG_]CATEGORY, [PKG_]REQUIRES, [PKG_]SUMMARY, and [PKG_]DESCRIPTION variables in the .cygport file itself, rather than having to maintain a set of files for each package. The next natural, albeit more difficult, step would be for cygport to automatically generate the requires for each (sub)package based on the algorithm used in cygport deps, similar to what rpmbuild does for binary packages. Of course, non-binary deps (e.g. commands called in scripts, or by fork(), etc.) would still have to be explicitly defined. Consider it on my todo list, but no guarantees as to when I'll get to it. Yaakov
