This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Download Directory Structure for setup.exe

----- Original Message -----
From: "Michael A Chase" <>
To: "Robert Collins" <>; "Cygwin-Apps"
Sent: Monday, January 21, 2002 3:54 PM
Subject: Download Directory Structure for setup.exe

> I've updated from CVS and built and used the last couple (2.175 and
> 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.

Cool. Any user level feedback while you're at it? Irrespective of recent
threads on cygwin@ I really do appreciate feedback!

> It appears that all new downloads, both setup.ini and package files,
now go
> to source specific subtrees, for example files from
> are saved
> under
> 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.

Yes. For clarity:
In install-from-net, only the setup.ini's from the selected mirror sites
are parsed. Cached tarballs in /latest and /contrib ARE used in addition
to anything in the relevant mirror site subdirs - if found.
In install-from-local, all setup.ini's in the subtree are scanned and
Cached tarballs from /latest and /contrib, and any subtree rooted where
a setup.ini is found are used.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]