Date: Sun, 1 Nov 1998 07:44:52 +0100 (CET) From: Leif Neland <leifn@swimsuit.internet.dk> To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl> Cc: Peter Wemm <peter@netplex.com.au>, freebsd-current@FreeBSD.ORG, Dmitry Valdov <dv@dv.ru> Subject: Re: kernel compile problem Message-ID: <Pine.BSF.4.05.9811010654560.3668-100000@gina.swimsuit.internet.dk> In-Reply-To: <XFMail.981031201737.asmodai@wxs.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
> > You got a cvsup in between commits.. Try again and you should be OK. > > just spotted this one too ;) > > How can ye make sure ye ain't between commits? cvsup it about 15-30 minutes > later and try again to make? > Is the problem that committing isn't 'atomical'? How about if the committer started by committing /usr/src/DONT_MAKE_WORLD_NOW then committed various stuff, then removed /usr/src/DONT_MAKE_WORLD_NOW This file could contain an explanation why the world shouldn't be made. The makefile should then check for the existance of this file. This could be implemented right now. It won't require updating cvsup and cvsupd. But this will give problems when several people are updating different parts of the tree... To make it more clean, it should be done in cvsupd and perhaps cvsup. It could be implemented by modifying using cvsupd's ability to check out the version of the tree as it were on a certain time. The committer sends it a command/file/signal, and then new additions made after that time is not seen by someone who requests the latest versions. After everything is committed, the committer removes the lock. Perhaps this should lock be on committer-resolution, so one committer forgetting a lock/being hit by an 18-wheeler won't lock the entire tree. If somebody _really_ wants the latest versions, one could specify an date=-1 or something instead of date=. What happens if somebody starts a cvsup, and files gets committed before the cvsup is finished? Are those updates seen? The tag date=. shouldn't mean "as late as possible", but "at the start of this cvsup-run", so to get a consistent snapshot of the tree. cvsupd should keep track of each clients starttime, and not supply later checkouts. 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?Pine.BSF.4.05.9811010654560.3668-100000>