X-Spam-Check-By: sourceware.org
Message-ID: <43D7875D.1050602@byu.net>
Date: Wed, 25 Jan 2006 07:12:45 -0700
From: Eric Blake <ebb9 AT byu DOT net>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: curses.h (Attn: bash and setup maintainers)
References: <20060120172639 DOT GA15196 AT brasko DOT net> <Pine DOT GSO DOT 4 DOT 63 DOT 0601201249200 DOT 9107 AT access1 DOT cims DOT nyu DOT edu> <20060121142951 DOT GA20108 AT brasko DOT net> <43D24CD0 DOT 5000508 AT byu DOT net> <20060121151547 DOT GD32082 AT brasko DOT net> <43D27E86 DOT 3010006 AT byu DOT net> <20060121201329 DOT GA9039 AT brasko DOT net> <Pine DOT GSO DOT 4 DOT 63 DOT 0601211730080 DOT 18707 AT access1 DOT cims DOT nyu DOT edu> <20060123145013 DOT GA9308 AT brasko DOT net> <Pine DOT GSO DOT 4 DOT 63 DOT 0601231104100 DOT 18707 AT access1 DOT cims DOT nyu DOT edu> <20060123161412 DOT GB9308 AT brasko DOT net> <Pine DOT GSO DOT 4 DOT 63 DOT 0601231116180 DOT 18707 AT access1 DOT cims DOT nyu DOT edu> <43D63084 DOT 7030302 AT byu DOT net> <Pine DOT GSO DOT 4 DOT 63 DOT 0601240922140 DOT 27934 AT access1 DOT cims DOT nyu DOT edu>
In-Reply-To: <Pine.GSO.4.63.0601240922140.27934@access1.cims.nyu.edu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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
>>g-b-s prep).
> 
> 
> 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
cygwin patches.

> 
> 
>>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
> properly.

OK, I'll stick with backwards compatibility for a while longer.

- --
Life is short - so eat dessert first!

Eric Blake             ebb9 AT byu DOT net
-----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

iD8DBQFD14dd84KuGfSFAYARAs4HAKDP2JlEpoW1eLF+ISmrV1N7/b8WJwCgztxC
cde7LPYlCIlhoApScUPawu8=
=l+5e
-----END PGP SIGNATURE-----

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/