Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Thu, 10 May 2001 17:03:58 -0400 Message-Id: <200105102103.RAA24464@envy.delorie.com> X-Authentication-Warning: envy.delorie.com: dj set sender to dj AT envy DOT delorie DOT com using -f From: DJ Delorie To: david DOT karr AT cacheflow DOT com CC: cygwin AT cygwin DOT com In-reply-to: <2C08D4EECBDED41184BB00D0B747334202FB439B AT exchanger DOT cacheflow DOT com> (david DOT karr AT cacheflow DOT com) Subject: Re: Storing a release/installation of Cygwin in a configuration manag ement system References: <2C08D4EECBDED41184BB00D0B747334202FB439B AT exchanger DOT cacheflow DOT com> > What sort of things can I do to facilitate this? I'd still like the ability > to update the "stored version" when I know there are changes I need, but in > general, I'd like the entire install package to be stored on our servers. Setup maintains a local snapshot of the ftp servers on your local hard drive. It actually installs from that. Just copy that area somewhere and do "install from local directory" for each additional installation. -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple