X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Message-ID: <485C3A04.6060705@bmts.com> Date: Fri, 20 Jun 2008 19:15:16 -0400 From: Ralph Hempel User-Agent: Thunderbird 2.0.0.6 (X11/20071022) MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: setup.exe command line parameters References: <485C0309.7080404@bmts.com> <485C044A.6010607@free.fr> In-Reply-To: <485C044A.6010607@free.fr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-brucetelecom.com-MailScanner-Information: Please contact Bruce Telecom 519.368.2000 for more information X-brucetelecom.com-MailScanner: Found to be clean X-brucetelecom.com-MailScanner-From: rhempel@bmts.com X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com 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? 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? Ralph -- 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/