This is the mail archive of the
mailing list for the Cygwin project.
Re: curses.h (Attn: bash and setup maintainers)
-----BEGIN PGP SIGNED MESSAGE-----
According to Igor Peshansky on 1/24/2006 7:26 AM:
>>Duly noted; bash-3.1-2 will improve on this situation (whenever I get
>>time to get that working; I'm still struggling with gracefully
>>incorporating upstream patches without wiping them out by rerunning
> Does <http://cygwin.com/ml/cygwin-apps/2006-01/msg00064.html> make sense?
Yes, but the devil is in the details. I'm trying to come up with some
sort of generic solution where you add a file
CYGWIN-PATCHES/upstream_patches.lst, whose contents (if the file exists)
is a list of patch files that should be bundled into the patch tarball,
and which should be applied before generating the cygwin-specific diff.
Then, based on the existance of CYGWIN-PATCHES/upstream_patchlist, g-b-s
would generate either a plain foo-1.1-1.patch (no upstream patches
provided), or a tarball foo-1.1-1.patch.tar.bz2 with both the upstream and
>>Actually, now that setup.exe has been updated to use /bin/bash and not
>>/bin/sh, the technical reason for me needing two postinstall scripts in
>>the first place has been overcome, so I may just simplify back to a
>>single script that does it all, rather than staging it through a .bat.
> You can't, unfortunately. Some people may have older versions of
> setup.exe on their systems, and blatantly disregard setup's warning that a
> newer version is available. Those systems will then fail to install sh
OK, I'll stick with backwards compatibility for a while longer.
Life is short - so eat dessert first!
Eric Blake firstname.lastname@example.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html