From owner-freebsd-hackers Wed Dec 18 22:00:20 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA02278 for hackers-outgoing; Wed, 18 Dec 1996 22:00:20 -0800 (PST) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id WAA02264 for ; Wed, 18 Dec 1996 22:00:16 -0800 (PST) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.3/8.8.3) with ESMTP id WAA29797 for ; Wed, 18 Dec 1996 22:00:14 -0800 (PST) Message-Id: <199612190600.WAA29797@austin.polstra.com> To: freebsd-hackers@freebsd.org Subject: Re: Correction: src-release and src-tools will REMAIN In-Reply-To: <59735o$j03@austin.polstra.com> References: <199612160453.UAA01018@austin.polstra.com> <59735o$j03@austin.polstra.com> Organization: Polstra & Co., Seattle, WA Date: Wed, 18 Dec 1996 22:00:14 -0800 From: John Polstra Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Sigh, this does not seem to be a good week for me to make announcements about things. I keep getting them wrong and having to post corrections. Here's the latest one: In article <59735o$j03@austin.polstra.com> I wrote: > The "src-release" and "src-tools" collections are going to remain > distinct from "src-etc". I am going to eliminate the overlap that > currently exists between src-etc and the other two, by modifying > what is included in src-etc. That is going to happen on freefall > this coming Saturday, December 21. > > There is going to be a hiccup when this happens. When sup and > CVSup notice the change to src-etc, they will proceed to delete > the affected files on the client machines. Most people won't care > about that. Neither src-release nor src-tools is really a part > of the system. If you want to continue to get them anyway, you'll > have to add those collections to your supfile. > > Here's the nasty part: If you have src-etc AND the other two in > your supfile, the files are going to be deleted (in connection with > src-etc) and then sent to you again (as part of src-release and > src-tools). Sorry, that's just the way things work under the sup > model. It doesn't recognize relationships between files in different > collections. I was suffering from faulty memory, and the above warning about files getting deleted is wrong, at least for CVSup. I tried it here, just to be sure, and the transition went very smoothly. No files got deleted. You don't have to take any special action to keep the files from being re-transmitted to you. In fact, if you want those files to be deleted, you're going to have to delete them manually. My error was in confusing what happens when a set of files is removed from a CVSup collection, as opposed to the physical files being removed from the repository itself. In the former case, CVSup leaves the files alone. They're not in the collection (any more), so CVSup is neither obligated nor permitted to do anything to them. Sorry for yet another false alarm. I'll go away and be quiet now. :-) -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth