Re: setup.exe command line parameters

Christopher Faylor wrote: If you are going to be discussing setup development you should subscribe to the cygwin-apps mailing list. I can't speak for the setup.exe developers but I suspect that you should be just using the CVS head for all of your development. Here's a case of a topic morphin

Re: setup.exe command line parameters

On Mon, Jun 23, 2008 at 08:17:42PM -0400, Ralph Hempel wrote: >Dave Korn wrote: >>Well, it needs a little debugging first, but it shouldn't be tricky to >>bash into shape. > >Sorry for taking so long, but here's what we have so far. The "newer" >patch referred to by Reini is against but the patch

Re: setup.exe command line parameters

Ralph Hempel wrote: Bad form, I know, but let me make the following sentence at least readable... 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

Re: setup.exe command line parameters

Dave Korn wrote: Well, it needs a little debugging first, but it shouldn't be tricky to bash into shape. Sorry for taking so long, but here's what we have so far. The "newer" patch referred to by Reini is against but the patch is against 2.590 which looks like it's a bout 2 point releases be

RE: setup.exe command line parameters

Ralph Hempel wrote on 23 June 2008 12:35: > Dave Korn wrote: > >> As it turns out that's the same patch by the same author only in an >> earlier stage of development! We'll go with the later version :) > > > Sorry if I'm trimming too much from the msgs... > > Are you saying that the patch p

Re: setup.exe command line parameters

Dave Korn wrote: As it turns out that's the same patch by the same author only in an earlier stage of development! We'll go with the later version :) Sorry if I'm trimming too much from the msgs... Are you saying that the patch pointed to by Reini is ready to be integrated into the curren

RE: setup.exe command line parameters

Ralph Hempel wrote on 23 June 2008 01:05: > Reini Urban wrote: > >> You mean the patch from >> http://thread.gmane.org/gmane.os.cygwin.applications/16502 ? > > I meant this one: > > > > Ralph As it turns out that's the same patch by

Re: setup.exe command line parameters

Reini Urban wrote: You mean the patch from http://thread.gmane.org/gmane.os.cygwin.applications/16502 ? I meant this one: Ralph -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.co

RE: setup.exe command line parameters

Reini Urban wrote on 22 June 2008 16:52: > Dave Korn schrieb: >> Ralph Hempel wrote on 20 June 2008 20:21: >>> Long story short, I ended up using a hacked older version of setup.exe >>> that accepted a -p parameter and a list of packages. It worked great! >>> >>> Is there a compelling reason why

Re: setup.exe command line parameters

Dave Korn schrieb: Ralph Hempel wrote on 20 June 2008 20:21: Long story short, I ended up using a hacked older version of setup.exe that accepted a -p parameter and a list of packages. It worked great! Is there a compelling reason why that patch can't be applied to the current setup and release

Re: setup.exe command line parameters

Ralph Hempel a écrit : cuicui wrote: You need to modify the "setup.ini" file, create "virtual" (empty) package that belongs to the "Base" category and make all the additional packages you want dependant of this virtual package by filling the "requires" field. Ok, so how do you keep the setup.

Re: setup.exe command line parameters

Dave Korn wrote: That being said, I CAN run setup.exe in unattended quiet mode and get a BASE cygwin install done, and I'm quite happy with that. But I'd really, really like to specify packages on the command line. Can I help by offering to update the patch to the current setup? Absolutely,

RE: setup.exe command line parameters

Ralph Hempel wrote on 20 June 2008 20:21: > Long story short, I ended up using a hacked older version of setup.exe > that accepted a -p parameter and a list of packages. It worked great! > > Is there a compelling reason why that patch can't be applied to the > current setup and released? Are ther

Re: setup.exe command line parameters

cuicui wrote: You need to modify the "setup.ini" file, create "virtual" (empty) package that belongs to the "Base" category and make all the additional packages you want dependant of this virtual package by filling the "requires" field. Ok, so how do you keep the setup.ini from being downloade

Re: setup.exe command line parameters

Ralph Hempel a écrit : With all of the talk about setup package selection and install procedures, I have a little story. One of the things I do for fun is write replacement firmware for the LEGO MINDSTORMS NXT - specifically pbLua. I needed an easy way to build the ARM7 cross compiler, and to lo

setup.exe command line parameters

With all of the talk about setup package selection and install procedures, I have a little story. One of the things I do for fun is write replacement firmware for the LEGO MINDSTORMS NXT - specifically pbLua. I needed an easy way to build the ARM7 cross compiler, and to locate and program the NXT