[ On Friday, July 12, 2002 at 16:54:15 (-0700), Bryan Bunch wrote: ]
> Subject: Newbie CVS commitinfo question
>
> I have a quick question about using the commitinfo admin file to
> perform a source-file check before commiting. Mabey the tool I should be
> using is Ageis (I've seen that project a lot in the archives), but what I
> want to do is have a script called at the beginning of the commit process
> which takes the following action:
No, you really do want to be using Aegis.
http://www.canb.auug.org.au/~millerp/aegis.html
Trying to do what you want to do with CVS is only going to end up being
a bad hack.
> So my initial thought is "why shouldn't the same user that has a global
> lock on the whole repository also be able to execute read-only operations
> like update or checkout that don't modify the repository's state?" My guess
> is that it's simply easier to do lock management if locks aren't
> "same-user-re-entrant" and no other cvs operations are allowed once the
> commit starts.
What does user identity have to do with repository integrity? The
repoisitory is not likely in a consistent state when it's locked. It
doesn't matter who locked it or who's trying to access it.
--
Greg A. Woods
+1 416 218-0098; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Planix, Inc. <[EMAIL PROTECTED]>; VE3TCP; Secrets of the Weird <[EMAIL PROTECTED]>
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
