RE: Installing from local directory -- trying to avoid massive duplication of effort
> -Original Message- > From: Bernard Dautrevaux [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, March 19, 2002 12:27 AM > Isn't there also entries in /etc/setup that may be needed to > be able to update later on? (of course in case we would like > to avoid full scripted re-install in case of upgrade or if > someone need one more package). Yes, and thus the concept of a scriptable setup.exe Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Installing from local directory -- trying to avoid massive duplication of effort
> -Original Message- > From: Phil Edwards [mailto:[EMAIL PROTECTED]] > Sent: Friday, March 15, 2002 8:27 PM > To: Jesper Eskilson > Cc: [EMAIL PROTECTED] > Subject: Re: Installing from local directory -- trying to > avoid massive > duplication of effort > > > On Fri, Mar 15, 2002 at 08:48:01AM +0100, Jesper Eskilson wrote: > > I've been looking for this script. Come to papa! ;-) > > > > Won't this leave out the necessary updates to the registry? > Or does mount > > take care of that? > > The latter; the only entries in the registry are the mount points. Isn't there also entries in /etc/setup that may be needed to be able to update later on? (of course in case we would like to avoid full scripted re-install in case of upgrade or if someone need one more package). Bernard Bernard Dautrevaux Microprocess Ingenierie 97 bis, rue de Colombes 92400 COURBEVOIE FRANCE Tel:+33 (0) 1 47 68 80 80 Fax:+33 (0) 1 47 88 97 85 e-mail: [EMAIL PROTECTED] [EMAIL PROTECTED] -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Installing from local directory -- trying to avoid massive duplication of effort
> -Original Message- > From: Phil Edwards [mailto:[EMAIL PROTECTED]] > Sent: Saturday, March 16, 2002 3:56 AM > To: Robert Collins > Cc: [EMAIL PROTECTED] > Subject: Re: Installing from local directory -- trying to > avoid massive duplication of effort > > > On Fri, Mar 15, 2002 at 11:16:03AM +1100, Robert Collins wrote: > > Or you could help contribute > > to the command line options for setup.exe. > > This was actually my first thought (I've been a GCC > contributor for years), but the CVS server was so overloaded > that I couldn't check out the winsup module. I finally gave > up and mailed the list. Kudos! Shame about CVS at the time then... Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Installing from local directory -- trying to avoid massive duplication of effort
On Fri, Mar 15, 2002 at 08:48:01AM +0100, Jesper Eskilson wrote: >Christopher Faylor <[EMAIL PROTECTED]> writes: > >> Either that or something like (untested): >> >> mkdir c:\cygwin >> cd c:\cygwin >> c:\whereever\tar xjf /cygdrive/c/whereever/cygwin-*.tar.bz2 >> mount -f -s -b c:/cygwin / >> mount -f -s -b c:/cygwin/lib /usr/lib >> mount -f -s -x -b c:/cygwin/bin /usr/bin >> c:\whereever\tar xjf /cygdrive/c/whereever/bash-*.tar.bz2 >> bin/bash >> for f in /cygdrive/c/whereever/*.tar.bz2; do >> case "$f" in >> cygwin-*) ;; >> bash-*) ;; >> *) /cygdrive/c/whereever/tar xjf $f ;; >> esac >> done >> cd /etc/postinstall >> for f in *.sh; do /bin/sh ./$f; done >> for f in *.bat; do cmd /c .\\$f; done >> exit > >I've been looking for this script. Come to papa! ;-) > >Won't this leave out the necessary updates to the registry? Or does mount >take care of that? Of course mount takes care of that. 'mount' predates setup.exe by many years. There is nothing magic in what setup.exe does. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Installing from local directory -- trying to avoid massive duplication of effort
On Fri, Mar 15, 2002 at 11:16:03AM +1100, Robert Collins wrote: > Or you could help contribute > to the command line options for setup.exe. This was actually my first thought (I've been a GCC contributor for years), but the CVS server was so overloaded that I couldn't check out the winsup module. I finally gave up and mailed the list. Phil -- If ye love wealth greater than liberty, the tranquility of servitude greater than the animating contest for freedom, go home and leave us in peace. We seek not your counsel, nor your arms. Crouch down and lick the hand that feeds you; and may posterity forget that ye were our countrymen.- Samuel Adams -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Installing from local directory -- trying to avoid massive duplication of effort
Christopher Faylor <[EMAIL PROTECTED]> writes: > Either that or something like (untested): > > mkdir c:\cygwin > cd c:\cygwin > c:\whereever\tar xjf /cygdrive/c/whereever/cygwin-*.tar.bz2 > mount -f -s -b c:/cygwin / > mount -f -s -b c:/cygwin/lib /usr/lib > mount -f -s -x -b c:/cygwin/bin /usr/bin > c:\whereever\tar xjf /cygdrive/c/whereever/bash-*.tar.bz2 > bin/bash > for f in /cygdrive/c/whereever/*.tar.bz2; do > case "$f" in > cygwin-*) ;; > bash-*) ;; > *) /cygdrive/c/whereever/tar xjf $f ;; > esac > done > cd /etc/postinstall > for f in *.sh; do /bin/sh ./$f; done > for f in *.bat; do cmd /c .\\$f; done > exit I've been looking for this script. Come to papa! ;-) Won't this leave out the necessary updates to the registry? Or does mount take care of that? -- /Jesper -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Installing from local directory -- trying to avoid massive duplication of effort
> -Original Message- > From: Phil Edwards [mailto:[EMAIL PROTECTED]] > Sent: Friday, March 15, 2002 6:52 AM > Is there a method, when using "install from > local," of simply installing every package that's present in > the local cache? Not in the current released setup. The next version has a more capable GUI that will allow full installs easily. Or you could help contribute to the command line options for setup.exe. Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Installing from local directory -- trying to avoid massive duplication of effort
Or with the next release of setup.exe, just 1) click on the top most category's "default" button, till it says install. 2) Click next. Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Installing from local directory -- trying to avoid massive duplication of effort
On Thu, Mar 14, 2002 at 03:25:36PM -0500, Phil Edwards wrote: >On Thu, Mar 14, 2002 at 03:03:35PM -0500, Christopher Faylor wrote: >> >But when running setup again and chosing the "install from local" >> >option, I have to make the same choices over again, not all of which I >> >remember (and it's a lot of clicking besides). Is there a method, when >> >using "install from local," of simply installing every package that's >> >present in the local cache? >> >> If I was doing this, I would just use shell scripts or bat files to >> install things and skip setup.exe. IMO, setup.exe isn't the appropriate >> tool for this job. A shell script or .bat job is. setup.exe is >> designed to be a tool for installing from the internet. Isn't intended >> to be used as a mass-deployment tool. There's too much potential for >> user error if you tell people to use setup.exe. > >Oh, it wouldn't be "people" using setup.exe; it would be me. Over and >over and over and over... And you're infallible? This is YA reason why you should just script this. >> However, I guess you could probably do what you need by creating your >> own setup.ini file: http://cygwin.com/setup.html . > >Hm... so, something like > >0) choose download-only mode >1) select the packages I want >2) download them >3) edit setup.ini and add 'Base' to the "category:" line for the >additional packages I want to install (and have downloaded) >4) on each client system, > 4a) make the package "cache" and edited setup.ini available > 4b) choose install-from-local >5) fervent invocation of deity > >I'll try this once my experimentatal-W2K box gets done thrashing around. Either that or something like (untested): mkdir c:\cygwin cd c:\cygwin c:\whereever\tar xjf /cygdrive/c/whereever/cygwin-*.tar.bz2 mount -f -s -b c:/cygwin / mount -f -s -b c:/cygwin/lib /usr/lib mount -f -s -x -b c:/cygwin/bin /usr/bin c:\whereever\tar xjf /cygdrive/c/whereever/bash-*.tar.bz2 bin/bash for f in /cygdrive/c/whereever/*.tar.bz2; do case "$f" in cygwin-*) ;; bash-*) ;; *) /cygdrive/c/whereever/tar xjf $f ;; esac done cd /etc/postinstall for f in *.sh; do /bin/sh ./$f; done for f in *.bat; do cmd /c .\\$f; done exit cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Installing from local directory -- trying to avoid massive duplication of effort
On Thu, Mar 14, 2002 at 03:03:35PM -0500, Christopher Faylor wrote: > >But when running setup again and chosing the "install from local" > >option, I have to make the same choices over again, not all of which I > >remember (and it's a lot of clicking besides). Is there a method, when > >using "install from local," of simply installing every package that's > >present in the local cache? > > If I was doing this, I would just use shell scripts or bat files to > install things and skip setup.exe. IMO, setup.exe isn't the appropriate > tool for this job. A shell script or .bat job is. setup.exe is > designed to be a tool for installing from the internet. Isn't intended > to be used as a mass-deployment tool. There's too much potential for > user error if you tell people to use setup.exe. Oh, it wouldn't be "people" using setup.exe; it would be me. Over and over and over and over... > However, I guess you could probably do what you need by creating your > own setup.ini file: http://cygwin.com/setup.html . Hm... so, something like 0) choose download-only mode 1) select the packages I want 2) download them 3) edit setup.ini and add 'Base' to the "category:" line for the additional packages I want to install (and have downloaded) 4) on each client system, 4a) make the package "cache" and edited setup.ini available 4b) choose install-from-local 5) fervent invocation of deity I'll try this once my experimentatal-W2K box gets done thrashing around. Phil -- If ye love wealth greater than liberty, the tranquility of servitude greater than the animating contest for freedom, go home and leave us in peace. We seek not your counsel, nor your arms. Crouch down and lick the hand that feeds you; and may posterity forget that ye were our countrymen.- Samuel Adams -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Installing from local directory -- trying to avoid massive duplication of effort
On Thu, Mar 14, 2002 at 02:51:38PM -0500, Phil Edwards wrote: >We need to install Cygwin on a /lot/ of W2K boxes, and we need to >include some packages not in the base set (openssh and its prereqs, for >one). To save time, I've done the "download from internet" option, >selected the things we need to install, and grabbed the packages. > >But when running setup again and chosing the "install from local" >option, I have to make the same choices over again, not all of which I >remember (and it's a lot of clicking besides). Is there a method, when >using "install from local," of simply installing every package that's >present in the local cache? If I was doing this, I would just use shell scripts or bat files to install things and skip setup.exe. IMO, setup.exe isn't the appropriate tool for this job. A shell script or .bat job is. setup.exe is designed to be a tool for installing from the internet. Isn't intended to be used as a mass-deployment tool. There's too much potential for user error if you tell people to use setup.exe. However, I guess you could probably do what you need by creating your own setup.ini file: http://cygwin.com/setup.html . cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Installing from local directory -- trying to avoid massive duplication of effort
The closest FAQ I could find was "How do I install everything?" which may or may not apply to my situation, I don't know. (I suspect it does, unfortunately.) We need to install Cygwin on a /lot/ of W2K boxes, and we need to include some packages not in the base set (openssh and its prereqs, for one). To save time, I've done the "download from internet" option, selected the things we need to install, and grabbed the packages. But when running setup again and chosing the "install from local" option, I have to make the same choices over again, not all of which I remember (and it's a lot of clicking besides). Is there a method, when using "install from local," of simply installing every package that's present in the local cache? Phil -- If ye love wealth greater than liberty, the tranquility of servitude greater than the animating contest for freedom, go home and leave us in peace. We seek not your counsel, nor your arms. Crouch down and lick the hand that feeds you; and may posterity forget that ye were our countrymen.- Samuel Adams -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
