Date: Sun, 13 Aug 2000 09:39:02 +0200 From: "Leif Neland" <leifn@neland.dk> To: "Mike Meyer" <mwm@mired.org>, <freebsd-current@FreeBSD.ORG> Cc: "Mike Meyer" <mwm@mired.org>, "Idea Receiver" <receiver@RedDust.BlueSky.net.au>, "Warner Losh" <imp@village.org> Subject: Re: Build breakage (was: fail to compile kernel...) Message-ID: <06e001c004fa$39e94d60$0e00a8c0@neland.dk> References: <14742.14082.837564.871879@guru.mired.org><Pine.BSF.4.10.10008131504560.77390-100000@RedDust.BlueSky.net.au><200008130553.XAA06673@harmony.village.org> <14742.15675.412839.269577@guru.mired.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> I didn't mean to finger you particularly. It's just a bit upsetting to > realize that I can't remember the last time I managed to do an update > to -current without some kind of breakage. I realize that -current > isn't guaranteed to build, but that's a bit ridiculous. I mean - I was > pleasantly surprised that I could build the world first time out. To > find the kernel breaking for a module that I have no absolutely no use > for on this machine was a bit upsetting. > > I'm beginning to wonder if I shouldn't use -stable as a buffer, and > just let the committers deals with things not being up to -current. Or > maybe check to see if the other *BSD's aren't a bit more demanding of > committers. > What if the machine building snapshots took a note of the time it cvsup'ped. Then if the build succeded, it would append this date to a file. We could then feed this date to our cvsup, to get a version which at least compiled. Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?06e001c004fa$39e94d60$0e00a8c0>