From owner-freebsd-hackers Mon Sep 2 10:47:34 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA04085 for hackers-outgoing; Mon, 2 Sep 1996 10:47:34 -0700 (PDT) Received: from eel.dataplex.net (eel.dataplex.net [208.2.87.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA04080; Mon, 2 Sep 1996 10:47:32 -0700 (PDT) Received: from [208.2.87.4] (cod [208.2.87.4]) by eel.dataplex.net (8.6.11/8.6.9) with SMTP id MAA27837; Mon, 2 Sep 1996 12:47:27 -0500 X-Sender: rkw@shark.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 2 Sep 1996 12:47:28 -0500 To: John Polstra From: rkw@dataplex.net (Richard Wackerbarth) Subject: Re: cvsup question, src/tools not updated, make release trouble Cc: hubs@freebsd.org, hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Richard Wackerbarth wrote: >One minor point: Paths like /pub/FreeBSD/FreeBSD-current are rather >FTP-specific. We already have a de-facto standard place for the >CVS repository, at /home/ncvs. And the sup control files are under >/home/sup, which we're more-or-less stuck with because it's hard-coded >into everybody's supfiles. But if we establish a new set of sup-files, who cares what "is in everybody's" The standard files will still apply only to someone who gets "everything". Otherwise, the update to the sup-files will destroy local modifications. > I'd propose that we standardize on /home/current or >/home/FreeBSD-current, and likewise for -stable. >Of course, those could be symlinks to whereever the mirror administrator >wanted to put the actual files. The argument AGAINST that standard is that the mirrors have to have the files in /pub anyway. The /home directory is usually under more administrative restriction than is the /pub space. Symlinks can go either way. Just because something has been done that way in the past is no real reason to continue it ad infinitum. Actually, to handle the "local" case, I guess that we should distribute a template that gets processed against the local specification file. The default specification file can be essentially an identity transform.