-----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 [EMAIL PROTECTED] -----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/
