From owner-freebsd-hackers Thu Feb 2 17:08:39 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id RAA26866 for hackers-outgoing; Thu, 2 Feb 1995 17:08:39 -0800 Received: from transarc.com (transarc.com [192.54.226.1]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id RAA26860 for ; Thu, 2 Feb 1995 17:08:38 -0800 Received: by transarc.com (5.54/3.15) id for hackers@freebsd.org; Thu, 2 Feb 95 20:08:33 EST Received: via switchmail; Thu, 2 Feb 1995 20:08:32 -0500 (EST) Received: from unix3 via qmail ID ; Thu, 2 Feb 1995 20:08:28 -0500 (EST) Received: from unix3 via qmail ID ; Thu, 2 Feb 1995 20:08:27 -0500 (EST) Received: from BatMail.robin.v2.12.CUILIB.3.45.SNAP.NOT.LINKED.unix3.sun4.40 via MS.5.6.unix3.sun4_40; Thu, 2 Feb 1995 20:08:27 -0500 (EST) Message-Id: Date: Thu, 2 Feb 1995 20:08:27 -0500 (EST) From: Pat_Barron@transarc.com To: hackers@FreeBSD.org Subject: Re: SUP must die, CTM for president !! In-Reply-To: <9502012135.AA19717@halloran-eldar.lcs.mit.edu> References: <29186.791616495@time.cdrom.com> <199502010755.XAA19507@ref.tfs.com> <9502012135.AA19717@halloran-eldar.lcs.mit.edu> Sender: hackers-owner@FreeBSD.org Precedence: bulk Garrett Wollman writes: > < > said: > > > But for src-current: > > It is stupid. Look at it: We run sup-scan every 8 hours, then > > we download individual sets of files to each user based on timestamps. > > That's not particular smart. We have probably all been hit by the > > zero byte file with the right timestamp havn't we ? > > It works great for me, and I've never had any problems with it that > weren't my fault. As I expressed in another message, I think the > problem is that there are simply too many people running -current, who > aren't prepared to deal with bleeding-edge phenomena. I must agree with this. I've never had a problem with SUP that wasn't actually a problem with some underlying system component. (Of course, I could be prejudiced, since I came from CMU and we used SUP for everything, so maybe I'm just accustomed to its quirks.....) As far as using SUP (or whatever) for -current, I'm really thankful that I have a mechanism like SUP to keep my source tree up to date; I don't like the idea of using a mechanism that only sends changes, since that stops me from being able to tweak my source tree between SUPs (like, if "make world" fails for some reason, and I want to fix it, but I expect there will be a "real" fix the next time I SUP) - something like CTM would prevent me from doing this, as I understand it. I certainly understand that the -current sources are a "work in progress" and the latest SUP of -current can't necessarily be considered as a "snapshot" - that the entire tree doesn't necessarily build at any given time. When I find problems I report them (just in case the problem is a genuine new bug, and not something that someone is in the middle of working on, or already knows about), sometimes I even fix them and send in fixes.... :-) Anyone who's not capable of and/or prepared to deal with the oddities that can be introduced by running the Release Du Jour should not be messing with -current. --Pat.