From owner-freebsd-ports  Fri Apr 21 19:56:36 1995
Return-Path: ports-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id TAA00217
          for ports-outgoing; Fri, 21 Apr 1995 19:56:36 -0700
Received: from indigo.csci.csusb.edu (nwestfal@indigo.csci.csusb.edu [139.182.38.28])
          by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id TAA00209
          ; Fri, 21 Apr 1995 19:56:32 -0700
Received: by indigo.csci.csusb.edu (931110.SGI/930416.SGI)
	for ports@freefall.cdrom.com id AA22532; Fri, 21 Apr 95 19:54:22 -0700
From: nwestfal@indigo.csci.csusb.edu (Neal Westfall)
Message-Id: <9504220254.AA22532@indigo.csci.csusb.edu>
Subject: Re: /usr/ports/distfiles - did I screw the pooch here?
To: jkh@freefall.cdrom.com (Jordan K. Hubbard)
Date: Fri, 21 Apr 1995 19:54:22 -0700 (PDT)
Cc: ports@freefall.cdrom.com
In-Reply-To: <27409.798513264@freefall.cdrom.com> from "Jordan K. Hubbard" at Apr 21, 95 06:14:24 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 860       
Sender: ports-owner@FreeBSD.org
Precedence: bulk

> It's beginning to occur to me that I kind of screwed up with the whole
> /usr/ports/distfiles idea.  It shouldn't be a directory, it should be
> a PATH!  Each element in the path should be scanned for R/W access
> (assuming it even exists) and put into a list so that the following
> behavior is exhibited:

Also, would it be too much to change the location of the distfiles so
that it isn't mixed in with the rest of the stuff?  This would make it
easier for people (like me!) who want to grab the entire ports tree but
not necessarily all the distfiles.  Currently the only way to do this
on wcarchive.cdrom.com or freefall.cdrom.com is to grab all the different
subtrees separately.  Those that have cdroms will already have most of the
distribution tarballs and may just want to grab the latest port fixes.

If this is out of line pay it no mind!

Neal