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 <cygwin AT cwilson DOT fastmail DOT fm>
User-Agent: Thunderbird 1.5 (Windows/20051201)
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> <43D7875D DOT 1050602 AT byu DOT 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 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

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/