[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Locking binary files?

From: Noel Yap
Subject: Re: Locking binary files?
Date: Wed, 8 May 2002 10:07:10 -0700 (PDT)

--- Nick Papadonis <address@hidden> wrote:
> Hi.  Another question.
> I  searched for this answer, however the only
> solution I
> found was using cvs edit.
> I would like to :
>   - Have CVS check out a modules files read only.
>   - Not allow any other user to concurrently work on
> a file when
> someone else is working on it.
> Is there a way to force this at CVSROOT?

Not really.  The closest you can get is if you
installed the "advisory locks" patch for "cvs edit"
and place "edit -c" and "commit -c" in everyone's
~/.cvsrc file.  These would abort an edit if another
edit exists and abort a checkin if no valid edit
exists, respectively.  The reason the "edit -c"
doesn't perfectly fit the requirements you state is
1. There's no enforcement of using the "-c" option.
2. "-f" can be supplied to override the "edit -c".

OTOH, this may be good enough for your needs.


Do You Yahoo!?
Yahoo! Health - your guide to health and wellness

reply via email to

[Prev in Thread] Current Thread [Next in Thread]