Take a look at the "cvs edit -c", "cvs edit -f", and "cvs ci -c" patches
available on SourceForge under the RCVS project. Note that "cvs edit -c" which
will check for other existing edits is done voluntarily by the client (ie there
is no absolute enforcement). However, with proper policies (which can easily be
promoted using .cvsrc) and good employees who follow those policies and
communicate among each other, "cvs edit -c" is enough of a "lock" while still
allowing concurrent development.
For example, let's say I decide to "cvs edit binary-file" ("edit -c" would be in
my ~/.cvsrc file). Someone (including me in another working area) later does
the same thing. That person will be blocked from the "cvs edit". That person
should then communicate to back to me (yes, I talk to myself sometimes ;-) to
figure out what's being done to the file and what the course of action should be
(we may very well decide that person should do a "cvs edit -f binary-file"). If
that person should decide to "cvs edit -f binary-file", I will get a
notification (via emal) of that action (if the server has been configured to do
so) whether or not that person has contacted me. Notification will also be sent
upon commits to the file.
The "cvs ci -c" patch ensures that the user has a valid edit on the file(s)
before proceeding with the commit.
This works out extremely well in our environment where we have developers in New
York and London.
Noel
[EMAIL PROTECTED] on 2000.08.11 06:29:05
To: [EMAIL PROTECTED]
cc: (bcc: Noel L Yap)
Subject: Strict locking
Hi all,
I have a small "problem" with CVS locking, which I could neither solve
with the Cederqvuist manual nor with the "Open Source Development with
CVS" book:
I want to enforce that users can't change the fileattributes from
readonly to write via 'cvs edit' if another user has set a lock on that
file or directory.
I have had a look at the rcslock.pl file in the contrib section of the
source distribution but it seems that the lock is honered only at the
time the 'cvs commit' is issued. I want 'cvs edit' to fail on files, on
which a lock was issued.
Thanks a lot for any info
Markus
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.
