From owner-freebsd-hackers Thu Oct 9 12:12:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA21978 for hackers-outgoing; Thu, 9 Oct 1997 12:12:18 -0700 (PDT) (envelope-from owner-freebsd-hackers) Received: from usr08.primenet.com (tlambert@usr08.primenet.com [206.165.6.208]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA21968 for ; Thu, 9 Oct 1997 12:12:14 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id MAA06915; Thu, 9 Oct 1997 12:11:29 -0700 (MST) From: Terry Lambert Message-Id: <199710091911.MAA06915@usr08.primenet.com> Subject: Re: group assignments from make world. To: imp@village.org (Warner Losh) Date: Thu, 9 Oct 1997 19:11:28 +0000 (GMT) Cc: jkh@time.cdrom.com, hackers@FreeBSD.ORG, fullermd@futuresouth.com In-Reply-To: <199710091807.MAA16908@harmony.village.org> from "Warner Losh" at Oct 9, 97 12:07:27 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > You have to get the password from -current monthly and place it in > /etc/current-pwd in order to build the system. If your password is > too old, it won't build. Experienced users can hack this out fairly > easily, and we'd not ship it by default. Minor hacking to the > makefile would be all that is needed. > > The other option is to have a current-urgent or current-build that > dealt only with issues having to do with builds. When a problem came > up, someone would cc current-build with that problem AND solution. > People could then make these into FAQ like entries and when the same > thing comes up again, pointers could be posted. > > Comments? Seems like an awful lot of work to get around a problem caused by allowing CVSup in the middle of a multifile checkin and/or checkin of code which hasn't been build between time of modification and time of checkin and/or multiple developers simultaneously adding code (a very rare, yet potential, collision case). Does this strike anyone else as a discipline issue rather than a user read-access control issue? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.