This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: cygport-0.9.3 in release-2
- From: Andrew Schulman <schulman dot andrew at epamail dot epa dot gov>
- To: cygwin-apps at cygwin dot com
- Date: Mon, 10 Nov 2008 10:38:01 -0500
- Subject: Re: cygport-0.9.3 in release-2
- References: <4906B2F8.4000708@users.sourceforge.net> <747eg4dsfpl4befpo8gb4qkgo3sm0d8fbi@4ax.com> <747eg4dsfpl4befpo8gb4qkgo3sm0d8fbi-e09XROE/p8c@public.gmane.org> <4907C0F1.2040005@cwilson.fastmail.fm> <a8ujg4lqsgvu01gtbns22dse6agt24ebgj@4ax.com> <a8ujg4lqsgvu01gtbns22dse6agt24ebgj-e09XROE/p8c@public.gmane.org> <49167C17.9050106@users.sourceforge.net>
> > 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.
OK, but what if instead of having my patch files clutter up the top-level
directory, I want to keep them tucked neatly away in patches/? (Which I do.)
Will cygport accept PATCH_URI=patches/* ?
> > 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.
I prefer to do it automatically, so I don't forget or have to do it manually
every time I rebuild (which I sometimes repeat several times from scratch, for
the same pkg-ver-rel). So should I do that at the start of src_compile(), or is
there a better place?
Thanks,
Andrew.