X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: <4939E651.BFEF677C@dessent.net> Date: Fri, 05 Dec 2008 18:41:21 -0800 From: Brian Dessent MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Setup.exe: all files in one common directory? (not per-server) References: <01b401c95743$52f4a580$3201a8c0 AT aew2knew> <4939DFD9 DOT 57A0178B AT dessent DOT net> <01f201c9574b$900043f0$3201a8c0 AT aew2knew> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com sowiso wrote: > and so on. __I cannot do anything about this.__ > You see? If I do want to avoid this, I must always use the same mirror. > And what if it's unaccessible due to a server downtime? Yes, when downloading it will create the files under the mirror's filename. That's by design because different mirrors can have different views of what the latest packages are (and thus different setup.ini files and so on.) What I'm saying is that later on when you do the "install from local dir" step you should be able to continue to specify F:\CygwinInstall\ as the local package directory and it should automatically recursively scan the contents of all the different mirror dirs found under that directory and offer to install the union of all of them. Brian -- 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/