X-Spam-Check-By:	sourceware.org
Message-ID:	<44FEC5AD.7030606@byu.net>
Date:	Wed, 06 Sep 2006 06:57:17 -0600
From:	Eric Blake <ebb9 AT byu DOT net>
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.5) Gecko/20060719 Thunderbird/1.5.0.5 Mnenhy/0.7.4.666
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	cygport question
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

I'm considering using cygport for the next release of bash.  However, I
can't seem to figure out how to make it do what I want:

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.

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

Eric Blake             ebb9 AT byu DOT net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFE/sWt84KuGfSFAYARApT8AJ9FgMrZEXBOlo3EPQ7EHYvtTb4qXgCfbP3W
0ffZhH4OfK7RxZ1UfvRLSOA=
=6g6s
-----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/

- Raw text -