Date: Mon, 02 Sep 1996 10:12:18 -0700 From: John Polstra <jdp@polstra.com> To: rkw@dataplex.net (Richard Wackerbarth) Cc: hubs@freebsd.org, hackers@freebsd.org Subject: Re: cvsup question, src/tools not updated, make release trouble Message-ID: <199609021712.KAA04329@austin.polstra.com> In-Reply-To: Your message of "Sun, 01 Sep 1996 18:52:34 CDT." <v02140b00ae4fd0e68826@[208.2.87.4]>
next in thread | previous in thread | raw e-mail | index | archive | help
Richard Wackerbarth wrote: > >It's because the mirror site you're using > >hasn't updated his sup configuration files recently. > > Which brings me back to a previous suggestion. > I think that we should standardize the location of the trees being "supped". > I suggest that they follow the general form of freefall and put them in > /pub/FreeBSD/FreeBSD-current, etc. > > If we do that, then the mirror sites can have a special distribution that > just gives them the appropriate sup control files. I agree with Richard. If the sup control files themselves were propagated to the mirrors automatically, then we wouldn't have these problems all the time. The current manual update-when-somebody-complains system is just too unreliable. Besides, anything we can do to make it easier to run a mirror site is a Good Thing. 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. 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. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199609021712.KAA04329>