Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com Message-ID: <392AD159.4DCBB8CA@cygnus.com> Date: Tue, 23 May 2000 11:43:37 -0700 From: Eric Christopher X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.3.99-pre5 i686) X-Accept-Language: en MIME-Version: 1.0 To: DJ Delorie CC: rdparker AT butlermfg DOT com, cygwin-developers AT sourceware DOT cygnus DOT com Subject: Re: setup: built-in tar References: <200005231735 DOT KAA02561 AT cygnus DOT com> <392ACE39 DOT 1158B5F5 AT cygnus DOT com> <200005231834 DOT OAA23819 AT envy DOT delorie DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit DJ Delorie wrote: > Last time I talked about this with RMS, the result was that the > minimum requirements be that it be on the same "site" (meaning same > machine or cluster and same protocol (ftp/http)) and available to the > user at the time the user downloaded the binary. I assume its > location can't be obscured. > > Beyond that is merely convenience. > > We don't need to keep sources around on FTP in case some user who > FTP'd a binary less than three years ago suddenly decides they need > the sources. That rule only applies to a 3b distribution; our ftp is > 3a. I should know better than to get in a conversation about this with you ;) Thanks for the explaination though. -eric