From owner-freebsd-current Sun Nov 1 02:00:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA05924 for freebsd-current-outgoing; Sun, 1 Nov 1998 02:00:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fep1-orange.clear.net.nz (fep1-orange.clear.net.nz [203.97.32.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA05908 for ; Sun, 1 Nov 1998 02:00:01 -0800 (PST) (envelope-from jabley@buddha.clear.net.nz) Received: from buddha.clear.net.nz (buddha.clear.net.nz [192.168.24.106]) by fep1-orange.clear.net.nz (1.5/1.11) with ESMTP id WAA08030; Sun, 1 Nov 1998 22:59:55 +1300 (NZDT) Received: (from jabley@localhost) by buddha.clear.net.nz (8.9.1/8.9.1) id WAA29924 for freebsd-current@freebsd.org; Sun, 1 Nov 1998 22:59:54 +1300 (NZDT) Message-ID: <19981101225954.A29897@clear.co.nz> Date: Sun, 1 Nov 1998 22:59:54 +1300 From: Joe Abley To: freebsd-current@FreeBSD.ORG Subject: Re: kernel compile problem References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Leif Neland on Sun, Nov 01, 1998 at 07:44:52AM +0100 X-Files: the Truth is Out There Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Nov 01, 1998 at 07:44:52AM +0100, Leif Neland wrote: > > 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... So we need a semaphore; however, a single lock file with a counter in it doesn't sound very practical for cvsup. How about a directory called "lock" in whatever part of the source tree is appropriate, into which committers deposit a file named with their e-mail address, containing a description of why the source tree is locked? bsd.subdir.mk could check for files within this subdirectory and fail quoting the contents of any files that are present. The same branch of the tree could be locked by more than one committer (since their respective lock files would have different names). Having lock directories at appropriate depths in the source tree would be better than one "don't make world" lock file -- that way if I want to rebuild and reinstall /usr/src/usr.bin/ I won't be affected by a transient commit lock in /usr/src/usr.sbin/ (for example). If no "lock" subdirectory is present, this should be interpreted as "there are no locks for this branch". Just an idea :) Whaddayathink? Joe -- Joe Abley Tel +64 9 912-4065, Fax +64 9 912-5008 Network Architect, CLEAR Net http://www.clear.net.nz/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message