X-Spam-Check-By: sourceware.org
Message-ID: <45037B0A.1060204@users.sourceforge.net>
Date: Sat, 09 Sep 2006 21:40:10 -0500
From: "Yaakov S (Cygwin Ports)" <yselkowitz AT users DOT sourceforge DOT net>
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: cygport question
References: <44FEC5AD DOT 7030606 AT byu DOT net>
In-Reply-To: <44FEC5AD.7030606@byu.net>
Content-Type: text/plain; charset=ISO-8859-1
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:
> bash ships as a primary tarball (3.1), then has several official patch
> files on top of the tarball (bash31-001 through bash31-017), so that bash
> 3.1.17 is the combination of these.  I know that I can add the patch files
> to the SRC_URI in my .cygport file, but how do I apply those patches to
> the original tree, so that the diff between my cygwin modifications and
> the original tree won't repeat the diffs of the official patch files?  It
> would be nice if there were a user-overridable hook called at the end of
> src_prep function that I could provide in my .cygport to merge the
> upstream patches into the original tree.

Right now there isn't a way to do this; I see that there should be, as
such code would benefit vim as well.  Let me work on this, but it may
not happen this week.

BTW, for anyone interested in cygport development, make sure you're
using CVS.  I'm really overdue for shipping 0.2.5 with a lot of new
features, including support for mirror:// SRC_URI's, Mono and Gtk#, git
repositories, and improvements to cygautoreconf and gnome2_autoreconf.


Yaakov


--
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/