This is the mail archive of the
mailing list for the Cygwin project.
Re: setup.exe command line parameters
- From: Reini Urban <rurban at x-ray dot at>
- To: cygwin-apps at cygwin dot com
- Date: Tue, 24 Jun 2008 17:08:12 +0200
- Subject: Re: setup.exe command line parameters
- References: <485C0309.email@example.com> <005601c8d39f$3e3cc550$2708a8c0@CAM.ARTIMI.COM> <485E7502.firstname.lastname@example.org> <485EE8C5.email@example.com> <003701c8d508$cf4aa750$2708a8c0@CAM.ARTIMI.COM> <485F8A81.firstname.lastname@example.org> <005a01c8d528$fa4197f0$2708a8c0@CAM.ARTIMI.COM> <4860EFE7.email@example.com> <4860F2C1.firstname.lastname@example.org> <00e901c8d5fd$6c5cc380$2708a8c0@CAM.ARTIMI.COM>
Dave Korn schrieb:
Ralph Hempel wrote on 24 June 2008 14:13:
Ummm this part makes no sense, so let me rephrase...
Sorry for taking so long, but here's what we have so far. The "newer"
patch referred to by Reini is against 2.590 which looks like it's
> about 2 point releases behind the current version in the
> 1.7 tree.
The current "released" version of setup is 2.573.2.2
So the question is, if I'm going to look at patching setup to accept
a list of packages on the command line, then which version should
we be merging the patches against?
The best thing to do is to work against CVS as explained at
in the section "Getting the source code from CVS and building".
The current three command-line patches at the tracker are all against
current HEAD and should applied in the following order:
$ quilt series