From owner-freebsd-ports  Tue Apr 25 06:49:20 1995
Return-Path: ports-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id GAA05505
          for ports-outgoing; Tue, 25 Apr 1995 06:49:20 -0700
Received: from ghpc6.ihf.rwth-aachen.de (ghpc6.ihf.RWTH-Aachen.DE [134.130.90.6])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id GAA05481
          ; Tue, 25 Apr 1995 06:49:07 -0700
Received: (from thomas@localhost) by ghpc6.ihf.rwth-aachen.de (8.6.8/8.6.6) id PAA25760; Tue, 25 Apr 1995 15:45:43 +0200
From: Thomas Gellekum <thomas@ghpc8.ihf.rwth-aachen.de>
Message-Id: <199504251345.PAA25760@ghpc6.ihf.rwth-aachen.de>
Subject: Re: /usr/ports/distfiles - did I screw the pooch here?
To: asami@cs.berkeley.edu (Satoshi Asami | =?ISO-2022-JP?B?GyRCQHUbKEI=?= =?ISO-2022-JP?B?GyRCOCsbKEIgGyRCOC0bKEI=?=)
Date: Tue, 25 Apr 1995 15:45:42 +0200 (MET DST)
Cc: thomas@ghpc8.ihf.rwth-aachen.de, scott@statsci.com, gpalmer@cdrom.com,
        jkh@freefall.cdrom.com, nwestfal@indigo.csci.csusb.edu,
        ports@freefall.cdrom.com
In-Reply-To: <199504250648.XAA03902@silvia.HIP.Berkeley.EDU> from "Satoshi Asami | =?ISO-2022-JP?B?GyRCQHUbKEI=?= =?ISO-2022-JP?B?GyRCOCsbKEIgGyRCOC0bKEI=?=" at Apr 24, 95 11:48:29 pm
Organization: Institut f. Hochfrequenztechnik, RWTH Aachen
X-Mailer: ELM [version 2.4 PL23]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Content-Length: 1901      
Sender: ports-owner@FreeBSD.org
Precedence: bulk

Satoshi Asami | =?ISO-2022-JP?B?GyRCQHUbKEI=?= =?ISO-2022-JP?B?GyRCOCsbKEIgGyRCOC0bKEI=?= wrote:
> 
>  * How about two separate directories (/usr/ports, /usr/distfiles)?
> 
> Well, where the user hold the distfiles on her system is irrelevant.

Correct me if I'm wrong, but at least this subthread was about the
possibility to grab ports/ on any old ftp site with `get
ports.tar.gz' and without getting all the distfiles, no?

Someone (Jordan?)  suggested using symlinks to keep the distfiles
out of ports/ and I think we have established now that this won't
work due to the configuration of some (many?)  sites.  I think one
possible solution is having two different directories, one for the
ports, one for the tarballs.  Of course you're right, where the user
keeps zir files _is_ irrelevant, but we'd have to decide on one
setup and let the user override it, if desired.

>  * This requires only one change in bsd.ports.mk (${DISTDIR} or what
>  * was that variable again?)  and you could get ports.tar.gz on any
>  * mirror, regardless of its configuration.
> 
> It's MASTER_SITES that is adding that directory on wcarchive as the
> fallback as the fallback when the port's specific one doesn't work.

OK, in the scheme above (two dirs) MASTER_SITES would be
ftp://ftp.freebsd.org/pub/FreeBSD/distfiles;
ftp://ftp.freebsd.org/pub/FreeBSD/ports would only contain the port
subdirs.  For easy setup I'd be using the same layout (at least as a
default) on the users disk (on the CD, in the distribution, ...),
overridable through ${DISTFILES} (which could be a path with a
default value of (in my scheme)
/usr/distfiles:/usr/local/distfiles:${HOME}/distfiles).  If the user
wants the same directory layout as in 2.0R, zie is free to link
/usr/ports/distfiles -> /usr/distfiles or set ${DISTFILES} directly.

Having said all this I just hope I'm not too far off the discussion
with my comments...

tg