This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: is there a standard way to get the g-b-s to apply multiple patches?
- From: Brian Dessent <brian at dessent dot net>
- To: cygwin-apps at cygwin dot com
- Date: Wed, 11 Jan 2006 06:03:49 -0800
- Subject: Re: is there a standard way to get the g-b-s to apply multiple patches?
- References: <20060111120053.GA716@efn.org> <43C50DBA.6070403@byu.net>
Eric Blake wrote:
> Take a look at bash and readline, where I distinguish between Chet Ramey's
> official upstream patches vs. my cygwin-specific patches; the
> bash-3.0-14.patch contains only my differences after the upstream patches
> have been applied. In particular, my modifications to g-b-s for bash
> 3.0-14 or readline 5.1-1 try to be pretty generic about bundling the
> upstream patches. If you find it useful, or have any improvements, then I
> can consider making the patch robust enough to propose for g-b-s itself.
I noticed that. However, there is one gotcha with this method. Because
the outermost -src tarball contains files that unpack into the upstream
source dir, this can cause confusion if you want to start over.
Example:
$ ./foo-1.0-1.sh prep conf build
# decide that for some reason you want to start over
$ rm -rf foo-1.0/
$ ./foo-1.0-1.sh prep conf build
However, the second build will not contain the Cygwin specific patches,
only the upstream patches. This is because they were deleted at the
"rm" step. To start over you have to re-unpack the toplevel -src
package, because it contains things that live under foo-1.0/.
Brian