This is the mail archive of the
cygwin-apps@cygwin.com
mailing list for the Cygwin project.
Re: avoiding a huge Cygwin patch
- From: Andrew Schulman <schulman dot andrew at epamail dot epa dot gov>
- To: cygwin-apps at cygwin dot com
- Date: Thu, 14 Oct 2004 15:48:16 -0400
- Subject: Re: avoiding a huge Cygwin patch
- Reply-to: schulman dot andrew at epamail dot epa dot gov
> > Is it acceptable to copy the
> > manuals in after creating the source patch, thereby excluding them from
> > the patch?
>
> Yes. You can add as many flags to the mkpatch() function as needed, e.g.
> -x 'additional-docs'
> when you put the documents intopp a directory called 'additional-docs'.
> Just make a note in the README where the documents are available, add
> the license for the docs (if different as the source licenses).
OK, that would work. Is 'additional-docs' a standard place for this, or
would something else like 'CYGWIN-EXTRAS' (easy to find next to
CYGWIN-PATCHES) also be okay?
> Maybe the best way to handle this would be a separate package with the
> manuals and, if available, with the documents source in a src package.
I'll look into this. Maybe more trouble than it's worth, or maybe not.
Thanks,
Andrew.