X-Spam-Check-By: sourceware.org Message-ID: <43D88F83.5060401@cwilson.fastmail.fm> Date: Thu, 26 Jan 2006 03:59:47 -0500 From: Charles Wilson User-Agent: Thunderbird 1.5 (Windows/20051201) 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> <43D7875D.1050602@byu.net> In-Reply-To: <43D7875D.1050602@byu.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 Eric Blake wrote: > 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. > Take a look at the build script for ncurses; it might contain some useful code. -- Chuck -- 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/