Re: Locking Command

[Paul Sander]

Why bother with locking at all when you have timestamps?  For copy-out
operations where you can identify all versions in advance (which you can
do with timestamps), you don't need locks because the versions can't be
altered after they've been committed.

So, wrap your "cvs checkout" command in a script that supplies the -D
option with the current time.  If you expect to be able to modify and
commit the files without doing an "update -A" first, then have your
script remove the sticky state from the CVS Entries files after the
checkout completes.

For copy-out operations where all affected versions can be identified in
advance (ideally by version number, or timestamp, but version tags can be
used only if they're not concurrently updated), you can even go straight to
the repository and safely copy out versions using straight RCS, assuming
that CVS uses the same copy/modify/rename method to update the ,v files,
and not even bother with CVS' directory level locking.  


--- Forwarded mail from address@hidden

Why do you want to do such a thing?

Assuming you really do want what you're asking, wrap CVS such that whenever you
do a checkout, it'll move the repository to a location accessible only by you.
Your shell script will also record where the moved repository is so that future
operations will work.  I know this is a very hackish solution, but yours is a
very odd request.

address@hidden on 2001.01.30 22:54:43

To:   address@hidden
cc:   (bcc: Noel L Yap)
Subject:  Locking Command

    I'm working under a CVS project. When I checked out the source
and do some modification at that time no one should have the access
to the Repository. For this what I have to do. Is there any Locking
methods. If there tell me how to Lock files in CVS.

--- End of forwarded message from address@hidden