X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Message-ID: <485D3DC6.7040002@free.fr>
Date: Sat, 21 Jun 2008 19:43:34 +0200
From: cuicui <cuicui DOT oizo AT free DOT fr>
User-Agent: Thunderbird 2.0.0.12 (X11/20080213)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: setup.exe command line parameters
References: <485C0309 DOT 7080404 AT bmts DOT com> <485C044A DOT 6010607 AT free DOT fr> <485C3A04 DOT 6060705 AT bmts DOT com>
In-Reply-To: <485C3A04.6060705@bmts.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

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.ini from being downloaded every time
> you connect to the server?

Mmm, I'm not sure there's an overlay mechanism, in my case I basically 
append the "virtual" package text at the end of the setup.ini everytime 
I collect a fresh package list.

> My plan is to have a c:\cygwinSetup directory on my local server,
> where I have the latest and greatest packages I need, and then
> on each machine (usually vmware machines) that I need to install on,
> I have a possibly different set of needs besides Base.
> 
> So one set of scripts grabs all the packages we need to the server, and
> the other set of scripts builds the cygwin installation on the local
> machines. This reduces the overall load on the mirrors.
> 
> I guess I'm actually implementing a local mirror for the packages, now
> that I think about it. Is there a way to limit the scope of the packages
> that I choose to mirror locally?

Maintaining a mirror simply consists in keeping the installation files 
in one place and sticking to a mirror for more convenience (otherwise a 
new directory named by the mirror URL is created in the repository).

The setup scopes the packages by itself as far as it's only downloading 
the packages you choose to install (+ the "base" packages).

Regards,

Nicolas

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/