This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
RE: setup.exe command line parameters
- From: "Dave Korn" <dave dot korn at artimi dot com>
- To: <cygwin-apps at cygwin dot com>
- Date: Tue, 24 Jun 2008 14:23:00 +0100
- Subject: RE: setup.exe command line parameters
- References: <485C0309.7080404@bmts.com> <005601c8d39f$3e3cc550$2708a8c0@CAM.ARTIMI.COM> <485E7502.3030200@x-ray.at> <485EE8C5.8010106@bmts.com> <003701c8d508$cf4aa750$2708a8c0@CAM.ARTIMI.COM> <485F8A81.5020407@bmts.com> <005a01c8d528$fa4197f0$2708a8c0@CAM.ARTIMI.COM> <4860EFE7.1060306@bmts.com> <4860F2C1.2000307@bmts.com>
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?
>>
>> Ralph
The best thing to do is to work against CVS as explained at
http://sourceware.org/cygwin-apps/setup.html
in the section "Getting the source code from CVS and building".
cheers,
DaveK
--
Can't think of a witty .sigline today....