Re: cvs edit -c locked checkout problem

[Robert J. Clark]

On Wed, 24 Apr 2002 10:28:37 -0400
"Krishnamoorthy, Balaji" <address@hidden>
wrote:
> -----Original Message-----
> From: Robert J. Clark [mailto:address@hidden
> Sent: Tuesday, April 23, 2002 7:36 PM
> To: address@hidden
> Cc: address@hidden
> Subject: Re: cvs edit -c locked checkout problem
> 
> 
> > On Tue, 23 Apr 2002 14:44:22 -0400
> > "Krishnamoorthy, Balaji" <address@hidden>
> > wrote:
> > 
> > > Hi All,
> > >     I have a CVS server setup in the Unix , all the users are
> > >     defined in the passwd file , of the repository . The CVSROOT is
> > >     as
> > >     ":cvspserver:address@hidden:/local/apps/cvs/samp
> > >     le apprepository" .And these repositories are defined in
> > >     cvsstart file .
> > > 
> > > The problem is 
> > > cvs edit -c for a locked checkout does not work. Any other user can
> > > unlock the file . 
> > > 
> > > Could anyone please suggest a workaround .
> 
> > Don't use CVS? The "C" in CVS stands for "Concurrent". This means that
> > anyone can edit any file at any time. If you need true locking, then
> > you will have to use one of the hacks floating around to add this to
> > CVS or live with the fact that CVS does not work that way.
> 
> Could you please suggest where I can find the patch to make one user
> unable to unlock the lock of the other user . Is it a good idea to put
> such patches ? what would be the implications if I would put in that .

    <http://mail.gnu.org/pipermail/info-cvs/2002-March/025504.html>
    <http://sourceforge.net/projects/rcvs/>

You will probably have to upgrade all clients and all servers to use this.

CVS was never designed to work this way. Try reading:

    <http://tech.indymedia.org/cvs_info/scenario.html>

and see if you can live with CVS merges instead of locks.

- Rob