From owner-freebsd-current Tue Sep 3 16:14:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA02798 for current-outgoing; Tue, 3 Sep 1996 16:14:18 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA02793 for ; Tue, 3 Sep 1996 16:14:16 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id QAA10759; Tue, 3 Sep 1996 16:12:52 -0700 (PDT) To: Terry Lambert cc: michaelh@cet.co.jp, kimc@w8hd.org, current@FreeBSD.org Subject: Re: Latest Current build failure In-reply-to: Your message of "Tue, 03 Sep 1996 11:08:57 PDT." <199609031808.LAA04620@phaeton.artisoft.com> Date: Tue, 03 Sep 1996 16:12:51 -0700 Message-ID: <10757.841792371@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Why do you need more than one build box? Is it because the snapshot > from the tree is made on each download request instead of on a timed > copy of the tree? Yes, the unreliability of the Internet, if nothing else, virtually guarantees that perfect syncronization is impossible. By collecting multiple votes, it's more possible to determine the last time at which it's reasonable to assume the tree still worked. > I think a more reasonable, one machine, version would be: > > 1) wait some interval > 2) copy active cvs tree to static cvs tree > 3) test-build static cvs tree > 4) if test-build fails, go to 1 > 5) copy successfully test-built static cvs tree to distribution > cvs tree > 6) people download distribution cvs tree That's assuming that you want to make one box both the build and the central distribution server, and that machine definitely isn't freefall.freebsd.org. Finding a new central distribution server would be too much perturberation. Jordan