Subj : Re: CVS Checkout Lock To : comp.programming From : =?iso-8859-1?q?Asbj=F8rn_S=E6b=F8?= Date : Wed Aug 17 2005 09:47 am "cholcomb" writes: > I am somewhat new to cvs and trying to set it up for a project. The > project manager wants to have it set up so that when you check out a > file it locks the file so noone else can check it out till you release > the file. Isn't that contrary to the whole idea of CVS? > >From what research I have done I can not fine out how to do this and > suspect it is not possible. > > My experince is the admin -L feature locks the file for checkin not > checkout. It seems the manual says that you can get reserved checkouts. See the middle of the first paragraph below (from the CVS info pages): ---------------------------------------- When more than one person works on a software project things often get complicated. Often, two people try to edit the same file simultaneously. One solution, known as "file locking" or "reserved checkouts", is to allow only one person to edit each file at a time. This is the only solution with some version control systems, including RCS and SCCS. Currently the usual way to get reserved checkouts with CVS is the `cvs admin -l' command (*note admin options::). This is not as nicely integrated into CVS as the watch features, described below, but it seems that most people with a need for reserved checkouts find it adequate. It also may be possible to use the watches features described below, together with suitable procedures (not enforced by software), to avoid having two people edit at the same time. The default model with CVS is known as "unreserved checkouts". In this model, developers can edit their own "working copy" of a file simultaneously. The first person that commits his changes has no automatic way of knowing that another has started to edit it. Others will get an error message when they try to commit the file. They must then use CVS commands to bring their working copy up to date with the repository revision. This process is almost automatic. --------------------------------------------- You are probably better helped by taking your question to the more suitable newsgroup comp.software.config-mgmt, or to the cvs mailing list (which I think is info-cvs@gnu.org). Asbjørn -- Asbjørn Sæbø, post.doc. Centre for Quantifiable Quality of Service in Communication Systems Norwegian University of Science and Technology .