This is the mail archive of the
cygwin-apps@cygwin.com
mailing list for the Cygwin project.
Re: avoiding a huge Cygwin patch
- From: Igor Pechtchanski <pechtcha at cs dot nyu dot edu>
- To: Andrew Schulman <schulman dot andrew at epamail dot epa dot gov>
- Cc: cygwin-apps at cygwin dot com
- Date: Thu, 14 Oct 2004 17:37:15 -0400 (EDT)
- Subject: Re: avoiding a huge Cygwin patch
- References: <200410141548.16275.schulman.andrew@epamail.epa.gov>
- Reply-to: cygwin-apps at cygwin dot com
On Thu, 14 Oct 2004, Andrew Schulman wrote:
> > > 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.
Actually, I think it might even be less trouble to create a separate docs
package than to try cramming extra binary files into the unison one, but
it's really up to you.
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ pechtcha@cs.nyu.edu
ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"Happiness lies in being privileged to work hard for long hours in doing
whatever you think is worth doing." -- Dr. Jubal Harshaw