Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
Date: Tue, 23 May 2000 14:34:57 -0400
Message-Id: <200005231834.OAA23819@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: echristo AT cygnus DOT com
CC: rdparker AT butlermfg DOT com, cygwin-developers AT sourceware DOT cygnus DOT com
In-reply-to: <392ACE39.1158B5F5@cygnus.com> (message from Eric Christopher on
	Tue, 23 May 2000 11:30:17 -0700)
Subject: Re: setup: built-in tar
References: <200005231735 DOT KAA02561 AT cygnus DOT com> <392ACE39 DOT 1158B5F5 AT cygnus DOT com>


> Yes, however, they should be in the same directory.  Preferably just
> shipping them along with the install is preferable.  Keeping some old
> set of sources around is just a pain.

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.