Take a look at the "cvs edit -c" and "cvs ci -c" patches available on
SourceForge under project RCVS.
The "cvs edit -c" patch will abort edits if someone else is editing the file.
"cvs edit -f" will force the edit. If an edit goes through, those watching the
file (eg also editing the file) will be notified. Watches must be turned on for
"cvs edit" to notify.
The "cvs ci -c" patch will abort commits if a valid edit isn't on a file.
Noel
[EMAIL PROTECTED] on 2000.05.30 18:28:26
To: [EMAIL PROTECTED]
cc: (bcc: Noel L Yap)
Subject: Re: CVS Users CVSROOT/passwd permissions
Well, after a bunch of testing it seems in this case that CVS
maintains user identity by what's in the CVSROOT/passwd file, which
means that the problem I thought I might have I don't have.
Unfortunately, I still do want to have users get exclusive use of
files when they check something out. Lots of binary files (gifs, jpgs,
mpgs) will be in use, but worse than that -- in my organization there
are liable to be multiple people working on the same file in the same
place at the same time when they shouldn't be. I want to use locks to
force people to talk to each other before they start editing, not
after...
I still don't have a satisfactory lock system in place, I must be
missing something. or maybe I need to write some perl to force any
person editing a file to lock it automatically?
--- In [EMAIL PROTECTED], "Noel L Yap" <[EMAIL PROTECTED]> wrote:
> Please reassess why you want to use locks. Once you move away from
reserved
> locks, CVS will be much easier to use.
>
> For example, it wouldn't matter whether both eater and feeder can
modify the
> files in your example, so long as they both know what'll be
happening to the
> files.
>
> Noel
>
>
>
>
> [EMAIL PROTECTED] on 05/30/2000 02:58:36 PM
>
> To: [EMAIL PROTECTED]
> cc: (bcc: Noel L Yap)
> Subject: CVS Users CVSROOT/passwd permissions
>
>
>
>
> I was hoping to not have to create UNIX user accounts on my CVS
> machine so for security I can just create user accounts in the
> CVSROOT/passwd file, which all act in UNIX as, say, user "cvs"...
But
> if I have user "feeder" which checks out and locks a file as user
> "cvs", will user "eater" be able to unlock the file and edit it?
> Though "eater" authenticates with a different password, "eater" is
> also using "cvs" as it's user on the UNIX system as shown in the
> passwd file.
>
> ie:
> > cat ~cvs/CVSROOT/passwd
>
> eater:lbAD1Z$oMX762:cvs
> feeder:$1$SNOFMmo5$/JLpY3Fi2lpa8KI4eTXC11:cvs
>
>
>
>
>
>
>
> This communication is for informational purposes only. It is not
intended as
> an offer or solicitation for the purchase or sale of any financial
instrument
> or as an official confirmation of any transaction. All market
prices, data
> and other information are not warranted as to completeness or
accuracy and
> are subject to change without notice. Any comments or statements
made herein
> do not necessarily reflect those of J.P. Morgan & Co. Incorporated,
its
> subsidiaries and affiliates.
This communication is for informational purposes only. It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan & Co. Incorporated, its
subsidiaries and affiliates.
