From owner-freebsd-hackers Thu Sep 25 20:32:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA03536 for hackers-outgoing; Thu, 25 Sep 1997 20:32:48 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA03529 for ; Thu, 25 Sep 1997 20:32:35 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id MAA00428; Fri, 26 Sep 1997 12:59:30 +0930 (CST) Message-Id: <199709260329.MAA00428@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Terry Lambert cc: mike@smith.net.au (Mike Smith), grog@lemis.com, hackers@FreeBSD.ORG Subject: Re: How do I check out a snapshot? In-reply-to: Your message of "Thu, 25 Sep 1997 21:47:44 GMT." <199709252147.OAA01744@usr04.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 26 Sep 1997 12:59:27 +0930 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > You don't. Due to the nature of the distributed CVS repository, there > > is a window where even the exact time of checkout for the snapshot > > build might leave you out of sync. The only way around this would be > > for the snap to be built from a tree directly checked out from the > > master repository. Jordan does this for the for-CDROM versions, I > > think. > > This is not due to the nature of the CVS repository; this is due to the > way it is being used. We've had the discussion about "how to use it > to close the window" before. Enforcing reader/writer locks by making > the repository group writable and the locking program SGID the caller > into the group would fix the problem, pronto. No, it wouldn't. Closer would be to claim the "checkout" time for a remotely-built SNAP matched the CVSup scan from which the remote repo was last updated, but unfortunately there isn't any such thing. mike