Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT cygwin DOT com Message-ID: <001401c1a237$c1ebc680$a100a8c0@mchasecompaq> From: "Michael A Chase" To: "Robert Collins" , "Cygwin-Apps" References: <20020118180305 DOT GA2312 AT dothill DOT com> <0a3501c1a074$07c97be0$0200a8c0 AT lifelesswks> Subject: Download Directory Structure for setup.exe Date: Sun, 20 Jan 2002 20:54:40 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 I've updated from CVS and built and used the last couple (2.175 and 2.176) setup.exe's. It will take me a while to get used to the new source organization and I wanted to check a few of my assumptions before I dig them out of the source. It appears that all new downloads, both setup.ini and package files, now go to source specific subtrees, for example files from ftp://ftp.mirrors.rcn.net/mirrors/sources.redhat.com/cygwin are saved in under ./ftp%3a%2f%2fmirrors.rcn.net%2fmirrors%2fsources.redhat.com%2fcygwin/. After setup.ini is downloaded from all candidates, either they are merged or the newest one is used. Likewise, the package file found in any subtree may be used for installing that package. -- Mac :}) ** I normally forward private questions to the appropriate mail list. ** Give a hobbit a fish and he eats fish for a day. Give a hobbit a ring and he eats fish for an age.