Skip site navigation (1)Skip section navigation (2)
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 !!
Message-ID:  <ojAM8=6SMV1b06t_oB@transarc.com>
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>

next in thread | previous in thread | raw e-mail | index | archive | help
Garrett Wollman <wollman@halloran-eldar.lcs.mit.edu> writes:
> <<On Tue, 31 Jan 1995 23:55:46 -0800 (PST), Poul-Henning Kamp <phk@ref.tfs.com\
> > 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.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ojAM8=6SMV1b06t_oB>