-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Andrew Schulman wrote: > Several of my packages require multiple patches to compile and run properly in > Cygwin. Instead of maintaining them all together as One Big Patch, I find it > easier to manage them as individual, discrete patch files, and apply them all > at > package build time.
I do that all the time. Just keep the patches in the same directory as the .cygport, and add their file names (just the basename, no full URI or path) to PATCH_URI. > I also have extra files, such as README and setup.hint, that I like to just > copy > in before building, instead of maintaining them as patches. Again, this is > easier for me in the long run. I don't think anybody maintains these as a patch; just copy them into CYGWIN-PATCHES sometime before the install step. I prefer to do this manually so that I'm sure to check/update them before packaging. > If there's a better way to do this, then I'm all ears. I hadn't thought of > doing it during compile() but that seems fine. src_compile() isn't meant for what you're trying to do here. Yaakov -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkkWfBcACgkQpiWmPGlmQSMk7QCffEpzYd8urS3rG9ycC/eSw9+z PEgAnRYjlF7FDhijGftnGj2/uV59+RzS =NcW0 -----END PGP SIGNATURE-----
