From owner-freebsd-current Tue Sep 3 18:09:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA12433 for current-outgoing; Tue, 3 Sep 1996 18:09:57 -0700 (PDT) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA12427 for ; Tue, 3 Sep 1996 18:09:52 -0700 (PDT) Received: from eel.dataplex.net by mail.crl.com with SMTP id AA24198 (5.65c/IDA-1.5 for ); Tue, 3 Sep 1996 18:08:23 -0700 Received: from [208.2.87.4] (cod [208.2.87.4]) by eel.dataplex.net (8.6.11/8.6.9) with SMTP id UAA21271; Tue, 3 Sep 1996 20:05:56 -0500 X-Sender: rkw@shark.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 3 Sep 1996 20:05:56 -0500 To: Terry Lambert From: rkw@dataplex.net (Richard Wackerbarth) Subject: Re: Latest Current build failure Cc: current@FreeBSD.org Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >Actually, you could seperate the process using a covert channel for the >checkout for the build server: > >2) copy active cvs tree on repository to statis cvs tree on > build server >5) copy successfully test-built static cvs tree on build server > to distribution cvs tree on distribution server (could be > the same machine, the repository, or could be a third machine) As I have said, we don't need to worry about the distribution of "cvs" trees. If I have such a tree, I can check out the (redefined) "current" distribution without worrying whether or not it is the "head" or if "head" is buildable at the present time. What we need to "limit" is the access known as "current". Updates of that version would be subject to the "buildability" test.