My general advice is to install the "cvs edit -c" patch and use the "cvs edit"
and family feature. "cvs edit -c" is like locks, but it can be overridden (via
"cvs edit -f") such that it's possible to have multiple people "locking" the
same file. In this respect, it's more a communication tool than a strict
locking tool. I haven't run into an environment where communication wasn't good
enough, though.
You may have problems doing the permissions stuff they want. It sounds like
your developers want features (ie locking) more than they want to solve a
problem (ie decrease amount of conflicts). You should try to convince them to
look more into what they're trying to achieve than to look for features they're
accustomed to. I know this could still be an uphill battle 'cos many people are
extremely stubborn and closed-minded.
If it matters, my environment used to be for old-style, strict locking. They
were open enough to give concurrent development a shot. Now they love it
(specially with the control that "cvs edit -c" affords).
Noel
Enc
(See attached file: edit-c.diff)
[EMAIL PROTECTED] on 03/06/2000 11:33:00 AM
To: [EMAIL PROTECTED]
cc: (bcc: Noel L Yap)
Subject: RCS style locking
Well, I've tried as hard as I can, but I can't convice our developers that
RCS locking is not necessary when using CVS. They're all old school, and
they don't trust CVS's ability to merge, nor do they claim they need it.
THey do however want the whole remote repository ability, which means I'm
in a hard spot. I need to figure out how to provide locking (every file
gets locked everytime it is checked out and unlocked everytime it is
commited.) Using CVS, or to provide a remote repository system using RCS.
Actually the developers even want to have a copy of the checked out source
all running in one directory on one of the UNIX servers. When they check
out they want the file's permissions in that directory to change so they
can access it untill the check it back in, then they want it to go to read
only for everyone. I'm not sure how possable any of this is. It seems
like what we really need is a client/server version of RCS. Anyone have
any advice, if nothing else can someone tell me how to do the locking. I
know this has come up before, but I don't really understand how the RCS
lock works, nor if it still works with CVS 1.10.8.
Thanks in advance for the help,
Ben Leibig
Systems Admin Consultant
mamamedia.com
edit-c.diff
