Date: Thu, 9 Oct 1997 19:11:28 +0000 (GMT) From: Terry Lambert <tlambert@primenet.com> To: imp@village.org (Warner Losh) Cc: jkh@time.cdrom.com, hackers@FreeBSD.ORG, fullermd@futuresouth.com Subject: Re: group assignments from make world. Message-ID: <199710091911.MAA06915@usr08.primenet.com> In-Reply-To: <199710091807.MAA16908@harmony.village.org> from "Warner Losh" at Oct 9, 97 12:07:27 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199710091911.MAA06915>