From owner-freebsd-current Mon Sep 2 17:31:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA21117 for current-outgoing; Mon, 2 Sep 1996 17:31:42 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA21112 for ; Mon, 2 Sep 1996 17:31:38 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.5/CET-v2.1) with SMTP id AAA28762; Tue, 3 Sep 1996 00:31:13 GMT Date: Tue, 3 Sep 1996 09:31:13 +0900 (JST) From: Michael Hancock Reply-To: Michael Hancock To: Terry Lambert cc: Kim Culhan , current@FreeBSD.org Subject: Re: Latest Current build failure In-Reply-To: <199609022126.OAA03091@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I haven't seen any real solutions to the buildable-current problem. Just to make it easy I'll describe 4 scenerios that break current. Note the order doesn't necessarily imply frequency of occurences. 1) Programmer commits code that wasn't tested well enough. 2) A change is made to a global resource such as a header file or a compile flag that breaks other programmer's code. 3) Operator error on the part of the (cv)sup user. 4) Corrupt CVS tree. REMEDIES 1) Buildable-current meister (Louie, Terry, or whoever volunteers) sends constructive criticism to programmer to shape up. Others will probably do the same, I will. 2) Assign global impact determination and resolution function to Buildable-current meister. CVS does not have the functionality to support this automatically, so additional tools are required. Perhaps the Buildable-current meister has UnixWare or Solaris and can mount to a FreeBSD box containing the Buildable sources and run cscope to determine the impact of the header file change. A Perl script is another solution. The Buildable-current meister has a programmer database and uses a custom script to automagically send mail to all programmers that the change will impact using the output of cscope or equivalent tool. The Buildable-current meister patiently collects all changes and does a make world and if make world is successful the tree is made available for public access. 3) Documentation. freebsd-current@freebsd.org cvs-all@freebsd.org. 4) Someone volunteers to write a utility that checks the integrity of the CVS repository. Does anyone else have any better ideas? I can think of other ways to do 2), but they all involve the assignment of a single Buildable-current meister. Regards, Mike Hancock