Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Message-ID: <02a401c18861$5f5ab570$0200a8c0@lifelesswks> From: "Robert Collins" To: , "cygwin-developers" References: Subject: Re: Is this the new format for the download directory Date: Wed, 19 Dec 2001 18:47:11 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" 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 X-OriginalArrivalTime: 19 Dec 2001 07:47:46.0740 (UTC) FILETIME=[731A6740:01C18861] === ----- Original Message ----- From: "Brian Keener" To: "cygwin-developers" Sent: Wednesday, December 19, 2001 3:32 AM Subject: Is this the new format for the download directory > I was just reviewing my download directory and cleaning up old archives and I > discovered this folder: > > ftp%3a%2f%2fmirrors.rcn.net%2fmirrors%2fsources.redhat.com%2fcygwin > > in my download local directory. Within my download directory I already had a > contrib and latest folder and now I see this new folder and in looking in it I > find a setup.ini and another latest folder. > > several questions pop up from this observation: > > 1) are my contrib and latest folders in my local directory no longer > necessary and Maybe. They are scanned if you have setup.ini in the directory above them, or no setup.ini in the whole tree. > 2) does the above new folder (which apparently relates to a mirror) mean I will > have a folder like this for every possible mirror I ever use :-( ( I really > hope not ) Yes. Do I like this - No. > 3) is a folder named this way really necessary. Sortof. We can put all the files in one flat directory per site, but that's kinda ugly. This is still in flux. Please feel free to suggest better approaches. Key design goals: 1) A downloaded set of files can be used for multiple installs. 2) Users can manually find tarballs easily (ie keep the file name intact). 3) The location of a given file needs to be deterministic (based on the setup.ini details). 4) We don't want to merge setup.ini's on the fly. We want them kept independent (at this point). 5) We don't want to mix files from independent sites into one directory structure. Why not? Licence issues. If someone has a setup.ini that advertises a problematically licenced program, IMO setup.exe shouldn't mix that in with the other programs. I.e. If I have a win32 (non-cygwin) tool that I licence to individuals, and they install by using setup.exe, that tool should not get dropped into a directory that they may give to friends etc. Another example of this would be an internal-only setup.ini that someone uses, and they don't want to have to manually clean out any relevant files time after time. Rob