(no subject)

[root]

>From address@hidden  Wed Feb 14 08:24:05 2001
>Return-Path: <address@hidden>
Received: from fencepost.gnu.org (fencepost.gnu.org [199.232.76.164])
        by gateway.camelot.jp (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id 
IAA15621
        for <address@hidden>; Wed, 14 Feb 2001 08:24:04 +0900
Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org)
        by fencepost.gnu.org with esmtp (Exim 3.16 #1 (Debian))
        id 14Soku-0004Yi-00; Tue, 13 Feb 2001 18:21:08 -0500
Received: from spock.ces.com ([198.202.205.28])
        by fencepost.gnu.org with esmtp (Exim 3.16 #1 (Debian))
        id 14Sojr-0004Wf-00
        for <address@hidden>; Tue, 13 Feb 2001 18:20:03 -0500
Received: from ces.com (devpc17.ces.com [198.202.205.135])
        by spock.ces.com (8.9.0/8.9.0) with ESMTP id RAA03756
        for <address@hidden>; Tue, 13 Feb 2001 17:20:01 -0600 (CST)
Message-ID: <address@hidden>
From: "David H. Thornley" <address@hidden>
Organization: CES International, Inc.
X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: address@hidden
Subject: Re: Strict Locking for checkouts
References: <address@hidden>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: address@hidden
Errors-To: address@hidden
X-BeenThere: address@hidden
X-Mailman-Version: 2.0
Precedence: bulk
List-Help: <mailto:address@hidden>
List-Post: <mailto:address@hidden>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/info-cvs>,
        <mailto:address@hidden>
List-Id: Announcements and discussions for the CVS version control system 
<info-cvs.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/info-cvs>,
        <mailto:address@hidden>
List-Archive: <http://mail.gnu.org/pipermail/info-cvs/>
Date: Tue, 13 Feb 2001 17:18:34 -0600
Status: O
Content-Length: 2258
Lines: 59



address@hidden wrote:
> 
>         I need to stablish a strict lock on each checkout on my repository,
> and then, when a user try to checkout a locked file, I need to denie
> access.
> 
Why?  What are you trying to accomplish by this?  As it stands,
CVS won't do what you say you need to do.  Since CVS has
been around for quite a few years, it would be reasonable to
think that was by design.

> 1- How can I automate the strinct locking creation? I cant not rely on
> users for this, I need some automated method to lock on each checout.
> 
Write wrapper scripts and tell the users to use those?

One problem here is that CVS has no operation that really
corresponds to a locking system's checkout.  You could look
at "cvs edit" and "cvs watch".  You can force all checkouts to
be of read-only files, and tell the users to use "cvs edit"
to change the permission.

In my experience, strict locking will buy you precisely nothing
over good communications.  Writing "I'm working on this, let
me know if you need to - David" in the master listing book
worked even better than having SCSS locks.

> 2- As I see rsclock only works for checkins.. how can I do to make
> this work on checkouts? In my implementation a user can not checkout a
> file if another user is working on it.
> 
Why not?

In some systems, there is a distinction between checking out a
file, thereby getting a copy and sole permission to change that
file, and some sort of copy, which gets a copy and no permission
to change the file.  In CVS, there is no such distinction.

If you really want to stop people from getting copies of files
other people are working on, then try some other system, because
CVS won't work for you.

Simply, CVS was designed to get away from this sort of
restriction.  The idea of merging changes together without
locks has proved very successful on many projects.  Why would
it not work on yours?

-- 
David H. Thornley                          Software Engineer
at CES International, Inc.:  address@hidden or (763)-694-2556
at home: (612)-623-0552 or address@hidden or
http://www.visi.com/~thornley/david/

_______________________________________________
Info-cvs mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/info-cvs