Re: [ITP] libIDL-0.8.3-1
Hi Yaakov, On Jul 22 17:40, Yaakov Selkowitz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Yaakov Selkowitz wrote: | I would like to contribute libIDL to the Cygwin distribution. This is a | prereq for ORBit2, one of the Gnome2 backend libraries. | | http://cygwin-ports.sourceforge.net/install/release/Gnome2/libIDL/libIDL-0.8.3-1-src.tar.bz2 | http://cygwin-ports.sourceforge.net/install/release/Gnome2/libIDL/libIDL-0.8.3-1.tar.bz2 | http://cygwin-ports.sourceforge.net/install/release/Gnome2/libIDL/setup.hint It's been a week now, and nobody's said a thing about this, with the exception of cgf's blanket vote for all core GNOME packages. Counting that as one vote, I'd like to give this my own GTG review, and as a contributor of 5 packages, would like to qualify for an exemption. ~ Corinna or cgf, objections? If not, could you upload? no objections from me or cgf, no. I've uploaded the package. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Co-Project Leader mailto:[EMAIL PROTECTED] Red Hat, Inc.
Re: BLT
On Jul 22 14:50, Marcus G. Daniels wrote: Hello, Here are Cygwin packages for the BLT Tcl/Tk Extension library, a fairly popular set of extension widgets for Tcl/Tk. These are for use with the native Tcl/Tk libraries, not X11 builds. http://www.santafe.edu/~mgd/cygwin/blt/blt-3.0-1-src.tar.bz2 http://www.santafe.edu/~mgd/cygwin/blt/blt-3.0-1.tar.bz2 Here is the setup.hint file: category: Libs requires: tcltk sdesc: Extension widgets for Tcl/Tk ldesc: BLT is an extension to the Tk toolkit, adding new widgets, geometry managers, and miscellaneous commands. Looks like a nice package so +1 from me. I've made a review and I'm a bit surprised about the content of usr/lib. There's a static lib called libBLT30.a and a symlink to ../bin/cygBLT30.dll, but there's no link library to link against the DLL, libBLT30.dll.a. Does that actually work for linking against the DLL? I thought the .dll.a lib is needed for that. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Co-Project Leader mailto:[EMAIL PROTECTED] Red Hat, Inc.
Re: BLT
Corinna Vinschen wrote: There's a static lib called libBLT30.a and a symlink to ../bin/cygBLT30.dll, but there's no link library to link against the DLL, libBLT30.dll.a. Does that actually work for linking against the DLL? I thought the .dll.a lib is needed for that. libtool (e.g. building clients of this library) looks for either a DLL or a import library. I just made a symlink because BLT didn't make the import library itself. The symlink is just so when clients go looking for BLT in lib/ they find something. I can make a .dll.a if you prefer. I just wanted to get feedback right away and so made this shortcut.. Thanks!
Re: BLT
On Jul 23 07:31, Marcus G. Daniels wrote: Corinna Vinschen wrote: There's a static lib called libBLT30.a and a symlink to ../bin/cygBLT30.dll, but there's no link library to link against the DLL, libBLT30.dll.a. Does that actually work for linking against the DLL? I thought the .dll.a lib is needed for that. libtool (e.g. building clients of this library) looks for either a DLL or a import library. I just made a symlink because BLT didn't make the import library itself. The symlink is just so when clients go looking for BLT in lib/ they find something. I can make a .dll.a if you prefer. I just wanted to get feedback right away and so made this shortcut.. Thanks! Yes, I would prefer a .dll.a file because that's the current scheme. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Co-Project Leader mailto:[EMAIL PROTECTED] Red Hat, Inc.
Re: BLT
Corinna Vinschen wrote: Yes, I would prefer a .dll.a file because that's the current scheme. Ok, done. Actually BLT had the command to do it, but the wrong target filename. Anyway now it makes a .dll.a, and the symlink for the .dll in lib/ is removed. http://www.santafe.edu/~mgd/cygwin/blt/ Thanks again. P.S. Any thoughts on HDF5? I need that for another package I'm making.
Re: BLT
On Jul 23 09:38, Marcus G. Daniels wrote: Corinna Vinschen wrote: Yes, I would prefer a .dll.a file because that's the current scheme. Ok, done. Actually BLT had the command to do it, but the wrong target filename. Anyway now it makes a .dll.a, and the symlink for the .dll in lib/ is removed. http://www.santafe.edu/~mgd/cygwin/blt/ Thank you. So we just need 2 more votes. P.S. Any thoughts on HDF5? I need that for another package I'm making. Not really. 3 votes and a GTG review required as usual. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Co-Project Leader mailto:[EMAIL PROTECTED] Red Hat, Inc.
[ANN] Updated: gmp-4.1.3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Big thanks to Gerrit P. Haase, who did 100% of the bugfixing and most of
the packaging work (I only had to correct one single bug).
Fails two tests ('bit' and 't-aorsmul') but shuold work much better than
previous package anyway, moreover I don't have tie to check it further
before I have my long dued holydays, so it would be a long time to have
a perfect package.
Ready at this address:
http://www.lapo.it/cygwin/gmp-4.1.3-2-src.tar.bz2
http://www.lapo.it/cygwin/gmp-4.1.3-2.tar.bz2
(version 2 because Gerrit's verison on his website is version 1, in case
anyone installed that one directly)
MD5SUM:
3efa66411988846cde5baf297ca0e085
717d57ea323812764d9636b2349cf281
SHA1SUM:
7887efa82323059d7224b5a5d4739281b46ce705
356bbefd01d9a6859612a91386a22d532047dbef
Lapo
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkEBS94ACgkQaJiCLMjyUvv+cACfaC+Xm52HTMQNxeHl0fUd01vk
zMwAniMEWBGl7ib46E1UDdgj3/kgjy6r
=gICE
-END PGP SIGNATURE-
approval procedure
Could someone direct me to a e-mail archive URL or web page that describes the approval procedure for packages? I understand there are three votes needed and a review of some kind. Who is eligible to vote and who is eligible to review? Thanks.
Re: approval procedure
On Fri, 23 Jul 2004, Marcus G. Daniels wrote: Could someone direct me to a e-mail archive URL or web page that describes the approval procedure for packages? Umm, I don't recall the exact link, but I can summarize it here. I suppose this information should be part of http://cygwin.com/setup.html#submitting... I understand there are three votes needed and a review of some kind. Yes. Who is eligible to vote and who is eligible to review? The current maintainers are eligible to vote. Anyone is eligible to do a review (other than the person proposing the package, except in some special cases). Igor P.S. FYI, he package proposal messages usually have ITP in the subject (see http://cygwin.com/acronyms/#ITP). -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! I have since come to realize that being between your mentor and his route to the bathroom is a major career booster. -- Patrick Naughton
Re: approval procedure
Igor Pechtchanski wrote: The current maintainers are eligible to vote. How does one go about generating interest for packages that the maintainers would be unlikely to use themselves? E.g. packages targeted for particular pre-existing scientific communities? Is advocacy appropriate on this list?
Re: approval procedure
On Fri, 23 Jul 2004, Marcus G. Daniels wrote: Igor Pechtchanski wrote: The current maintainers are eligible to vote. How does one go about generating interest for packages that the maintainers would be unlikely to use themselves? E.g. packages targeted for particular pre-existing scientific communities? Is advocacy appropriate on this list? One of the attributes of an ideal maintainer is having a feel for what packages would be useful for the community, even though she would not use them herself. :-) It might help if you included some info about where a particularly obscure package was leading (e.g., I have no idea what HDF5 is or does, but I may have heard of the other package you intend to produce that requires it). The original ITP message is a good place to include any justification or advocacy you may have for the package. On the other extreme, I doubt bombarding the list with advocacy or vote soliciation messages every day or so is going to endear you to the maintainers. :-) Also, maintainers are usually a busy lot, and you can't really expect the votes only one day after an ITP. If worse comes to worst and you don't get the votes (probably because the maintainers assume that there aren't many members of the target community using Cygwin), you can host your own package server with just those packages that weren't accepted (see http://sources.redhat.com/cygwin-apps/package-server.html)... Oh, and if some package does get the votes, all of its prerequisites are more or less automatically accepted... Hope this helps, Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! I have since come to realize that being between your mentor and his route to the bathroom is a major career booster. -- Patrick Naughton
Re: approval procedure
Igor Pechtchanski wrote: It might help if you included some info about where a particularly obscure package was leading (e.g., I have no idea what HDF5 is or does, but I may have heard of the other package you intend to produce that requires it). HDF5 is a library for fast and efficient storage and recovery of dimensional data. Unlike SQL RDBMs, it is mainly concerned with the portable and efficient storage of large datasets, often of many dimensions (space, time, temperature, etc). Although the kind of queries that can be made are a subset of what one can do with an RDBMS, it is much faster, typically keeping the data in the native representation of the machine (suitably annotated). Then if the HDF5 file is given to someone else, the library automatically converts to the right representation via the API. There are many features in the library including non-trivial data structures like ragged arrays and compound data types, support for different pluggable compression techniques, ability to operate `over a wire' in cluster computing environments, etc. but the basic idea is that is a portable way to have fast, random access to big chunks of dimensional data. (Something you don't have with a text file, say.) It might help if you included some info about where a particularly obscure package was leading The other package I'm working on is a simulator for agent-based modeling (http://www.swarm.org). HDF5 is useful to this package because it provides a way to record the evolving state of a simulation and to load different sets of initial conditions (e.g. geographical maps). Thanks for the tip about the package-server.
Please upload: ssmtp-2.60.9-2
Please upload a new version of ssmtp: http://math.berkeley.edu/~schneck/cygwin/ssmtp/ssmtp-2.60.9-2.tar.bz2 http://math.berkeley.edu/~schneck/cygwin/ssmtp/ssmtp-2.60.9-2-src.tar.bz2 Corinna, this has an ssmtp-config which suggests linking /usr/sbin/sendmail to ssmtp; so go ahead and upload your new cron. Thanks! Robert
[ITP] Swarm
Hello, Here are Cygwin packages for the Swarm simulation system, a library that facilitates construction of agent-based models. The packages are available here: http://www.santafe.edu/~mgd/cygwin/swarm Here's the setup.hint file: category: Libs requires: blt tcltk libpng12 hdf5 gcc-objc cygwin sdesc: Multi-agent simulation library ldesc: Swarm is a software package for multi-agent simulation of complex systems. The basic architecture of Swarm is the simulation of collections of concurrently interacting agents.
Please upload: exim-4.41-1
This is a bug fix release, replacing 4.40-2 http://mysite.verizon.net/phumblet/exim-4.41-1/exim-4.41-1-src.tar.bz2 http://mysite.verizon.net/phumblet/exim-4.41-1/exim-4.41-1.tar.bz2 http://mysite.verizon.net/phumblet/exim-4.41-1/setup.hint Thanks Pierre
Re: approval procedure
On Fri, Jul 23, 2004 at 12:44:09PM -0600, Marcus G. Daniels wrote: Igor Pechtchanski wrote: The current maintainers are eligible to vote. How does one go about generating interest for packages that the maintainers would be unlikely to use themselves? E.g. packages targeted for particular pre-existing scientific communities? Is advocacy appropriate on this list? bribes?
Re: Please upload: ssmtp-2.60.9-2
On Fri, Jul 23, 2004 at 03:42:44PM -0400, Robert R Schneck-McConnell wrote: Please upload a new version of ssmtp: http://math.berkeley.edu/~schneck/cygwin/ssmtp/ssmtp-2.60.9-2.tar.bz2 http://math.berkeley.edu/~schneck/cygwin/ssmtp/ssmtp-2.60.9-2-src.tar.bz2 Corinna, this has an ssmtp-config which suggests linking /usr/sbin/sendmail to ssmtp; so go ahead and upload your new cron. I've downloaded this to sourceware.org. Which of the old ssmtp files should be deleted, if any: -rw-rw-r--1 cyguser cygwin 46738 Feb 18 21:34 ssmtp-2.60.4-3-src.tar.bz2 -rw-rw-r--1 cyguser cygwin 22325 Feb 18 21:35 ssmtp-2.60.4-3.tar.bz2 -rw-rw-r--1 cyguser cygwin 51851 Jun 3 19:53 ssmtp-2.60.9-1-src.tar.bz2 -rw-rw-r--1 cyguser cygwin 23985 Jun 3 19:53 ssmtp-2.60.9-1.tar.bz2 -rw-r--r--1 root cygwin 53586 Jul 24 01:35 ssmtp-2.60.9-2-src.tar.bz2 -rw-r--r--1 root cygwin 24486 Jul 24 01:35 ssmtp-2.60.9-2.tar.bz2 ?
Re: Please upload: exim-4.41-1
On Fri, Jul 23, 2004 at 07:16:33PM -0400, Pierre A. Humblet wrote: This is a bug fix release, replacing 4.40-2 http://mysite.verizon.net/phumblet/exim-4.41-1/exim-4.41-1-src.tar.bz2 http://mysite.verizon.net/phumblet/exim-4.41-1/exim-4.41-1.tar.bz2 http://mysite.verizon.net/phumblet/exim-4.41-1/setup.hint Uploaded. Deleted exim-4.34*.tar.bz2. Thanks. cgf
Re: Please upload: exim-4.41-1
At 09:37 PM 7/23/2004 -0400, you wrote: On Fri, Jul 23, 2004 at 07:16:33PM -0400, Pierre A. Humblet wrote: This is a bug fix release, replacing 4.40-2 http://mysite.verizon.net/phumblet/exim-4.41-1/exim-4.41-1-src.tar.bz2 http://mysite.verizon.net/phumblet/exim-4.41-1/exim-4.41-1.tar.bz2 http://mysite.verizon.net/phumblet/exim-4.41-1/setup.hint Uploaded. Deleted exim-4.34*.tar.bz2. Thanks, but I was hoping to get rid of the buggy 4.40 instead. Could you restore 4.34? It's being uploaded to http://mysite.verizon.net/phumblet/exim-4.34-1/exim-4.34-1-src.tar.bz2 http://mysite.verizon.net/phumblet/exim-4.34-1/exim-4.34-1.tar.bz2 http://mysite.verizon.net/phumblet/exim-4.34-1/setup.hint Pierre
Re: Please upload: exim-4.41-1
On Fri, Jul 23, 2004 at 09:41:35PM -0400, Pierre A. Humblet wrote: At 09:37 PM 7/23/2004 -0400, you wrote: On Fri, Jul 23, 2004 at 07:16:33PM -0400, Pierre A. Humblet wrote: This is a bug fix release, replacing 4.40-2 http://mysite.verizon.net/phumblet/exim-4.41-1/exim-4.41-1-src.tar.bz2 http://mysite.verizon.net/phumblet/exim-4.41-1/exim-4.41-1.tar.bz2 http://mysite.verizon.net/phumblet/exim-4.41-1/setup.hint Uploaded. Deleted exim-4.34*.tar.bz2. Thanks, but I was hoping to get rid of the buggy 4.40 instead. I should have read your original message more closely. Sorry. Could you restore 4.34? It's being uploaded to http://mysite.verizon.net/phumblet/exim-4.34-1/exim-4.34-1-src.tar.bz2 http://mysite.verizon.net/phumblet/exim-4.34-1/exim-4.34-1.tar.bz2 http://mysite.verizon.net/phumblet/exim-4.34-1/setup.hint Yup, done. cgf
Re: Please upload: ssmtp-2.60.9-2
Christopher Faylor wrote: On Fri, Jul 23, 2004 at 03:42:44PM -0400, Robert R Schneck-McConnell wrote: Please upload a new version of ssmtp: I've downloaded this to sourceware.org. Which of the old ssmtp files should be deleted, if any: -rw-rw-r--1 cyguser cygwin 46738 Feb 18 21:34 ssmtp-2.60.4-3-src.tar.bz2 -rw-rw-r--1 cyguser cygwin 22325 Feb 18 21:35 ssmtp-2.60.4-3.tar.bz2 -rw-rw-r--1 cyguser cygwin 51851 Jun 3 19:53 ssmtp-2.60.9-1-src.tar.bz2 -rw-rw-r--1 cyguser cygwin 23985 Jun 3 19:53 ssmtp-2.60.9-1.tar.bz2 -rw-r--r--1 root cygwin 53586 Jul 24 01:35 ssmtp-2.60.9-2-src.tar.bz2 -rw-r--r--1 root cygwin 24486 Jul 24 01:35 ssmtp-2.60.9-2.tar.bz2 Delete 2.60.9-1. Thanks! Robert
Re: Please upload: ssmtp-2.60.9-2
On Fri, Jul 23, 2004 at 10:20:57PM -0400, Robert R Schneck-McConnell wrote: Christopher Faylor wrote: On Fri, Jul 23, 2004 at 03:42:44PM -0400, Robert R Schneck-McConnell wrote: Please upload a new version of ssmtp: I've downloaded this to sourceware.org. Which of the old ssmtp files should be deleted, if any: -rw-rw-r--1 cyguser cygwin 46738 Feb 18 21:34 ssmtp-2.60.4-3-src.tar.bz2 -rw-rw-r--1 cyguser cygwin 22325 Feb 18 21:35 ssmtp-2.60.4-3.tar.bz2 -rw-rw-r--1 cyguser cygwin 51851 Jun 3 19:53 ssmtp-2.60.9-1-src.tar.bz2 -rw-rw-r--1 cyguser cygwin 23985 Jun 3 19:53 ssmtp-2.60.9-1.tar.bz2 -rw-r--r--1 root cygwin 53586 Jul 24 01:35 ssmtp-2.60.9-2-src.tar.bz2 -rw-r--r--1 root cygwin 24486 Jul 24 01:35 ssmtp-2.60.9-2.tar.bz2 Delete 2.60.9-1. Thanks! Done. cgf (who needs something productive and mindless to do right now)
