-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Charles Wilson wrote: > Okay, so these are (mostly) your own custom patches needed to port the > code to cygwin, and not "official" patches from somewhere else, like > > 1) bugfixes taken wholesale from another distro > (http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-libs/ncurses/files/) > 2) intra-release patches (see ftp://invisible-island.net/ncurses/5.6/) > > If it were 1) or 2), I'd suggest using > > PATCH_URI="http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-libs/ncurses/files/ncurses-5.6-build.patch > > ftp://invisible-island.net/ncurses/5.6/ncurses-5.6-coverity.patch.gz";
BTW, that's mirror://portage/sys-libs/ncurses/... for short, but you've got the idea. > a) my example, ncurses, has a LOT (50 or so) "official" patches > b) they are all gz-compressed; cygport might not support compressed > patches in PATCH_URI Compressed single patches are supported in PATCH_URI since 0.3.5. > So, in fact, for ncurses (where some of the official upstream "patches" > are actually shell scripts with shar-compressed patches!) I actually > DON'T specify these files in PATCH_URI. Instead, I specify them in > SRC_URI, and then use src_unpack_hook to apply (that is, execute!) them. Interesting, I'd like to see those "patches"; with the recent release of ncurses-5.7, all the 5.6 patches are gone. > Yaakov? Pretty please? I think you know that I haven't been a big fan of this idea. Nevertheless, cygport 0.9.x allows you to call src_compile(), src_install(), or any self-defined function on the command line, but it doesn't allow for any arguments to the function. Adding that limitation made the implementation much easier than what you were proposing, and I hope that it will be sufficient. Yaakov -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkkWgHAACgkQpiWmPGlmQSMO6wCZAYYFbbjEz7ufFJ5fkdJHXslc 3c4AoOCOv5aK+iO/Q2+3Z0g0p+f+A5vV =/NPh -----END PGP SIGNATURE-----
