X-Spam-Check-By: sourceware.org Message-ID: <43D7875D.1050602@byu.net> Date: Wed, 25 Jan 2006 07:12:45 -0700 From: Eric Blake User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: curses.h (Attn: bash and setup maintainers) References: <20060120172639.GA15196@brasko.net> <20060121142951.GA20108@brasko.net> <43D24CD0.5000508@byu.net> <20060121151547.GD32082@brasko.net> <43D27E86.3010006@byu.net> <20060121201329.GA9039@brasko.net> <20060123145013.GA9308@brasko.net> <20060123161412.GB9308@brasko.net> <43D63084.7030302@byu.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.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 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@byu.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/