Re: cygport question

["Yaakov S (Cygwin Ports)" <yselkowitz at users dot sourceforge dot net>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Yaakov S (Cygwin Ports) wrote:
> 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.

What an understatement.

Please try the PATCH_URI feature in CVS HEAD, and see
ports/apps/vim/gvim-7.0.178-1 for an example.


Yaakov
Cygwin Ports
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD4DBQFFi42qpiWmPGlmQSMRCAjAAKDsn1zBiRq90oXjDwMGQDROXT39QwCXThNx
Sw+/jbDH878dR5n4m702pA==
=K1jl
-----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/