[Cvsnt] Unable to lock files

Antoniosi, Luis Felipe felipe.antoniosi at softcomex.com.br
Thu Apr 4 19:57:40 BST 2002


Hi,

Finally I got how to grant allow non-machine/domain administrator users to
lock files on the repository.
Just add the file admin in the cvsroot and include the usernames one for
each line. But the file must be added directly, without adding by cvs
commands.

Felipe.


-----Original Message-----
From: Bo Berglund [mailto:bosse at agiusa.com]
Sent: Wednesday, April 03, 2002 6:55 PM
To: 'Antoniosi, Luis Felipe'
Subject: RE: [Cvsnt] Unable to lock files


I don't think so.
CVS was designed to be an unlocked system so the locks are just hints
really.
There is nothing that can stop a developer from modifying a file even if it
is
"locked", just change the readonly property and edit away.
CVS has no control over what happens on the client side really.

It's a pity that files like these (and MS Word documents too) cannot be
handled
like plain text files...

/Bo


-----Original Message-----
From: Antoniosi, Luis Felipe [mailto:felipe.antoniosi at softcomex.com.br]
Sent: den 3 april 2002 21:14
To: bo.berglund at telia.com; cvsnt at cvsnt.org
Subject: RE: [Cvsnt] Unable to lock files


Hello,

Thanks for you suggestion, but in fact I wouldn't wish to change the system.
The cvs works fine on my sources if no merge is done.
But, is it possible to lock the files without being domain/machine
administrator in pserver mode?

-----Original Message-----
From: cvsnt-admin at cvsnt.org [mailto:cvsnt-admin at cvsnt.org]On Behalf Of
Bo Berglund
Sent: Wednesday, April 03, 2002 3:20 PM
To: cvsnt at cvsnt.org
Subject: Re: [Cvsnt] Unable to lock files


On Wed, 3 Apr 2002 12:50:49 +0000 (UTC), "Antoniosi, Luis Felipe"
<felipe.antoniosi at sfw.com.br> wrote:

>Hello,
>
>Let me explain my problem:
>
>We develop on SQLWindows32, which doesn't produce source codes in plain
text
>like any other languange. Due to this the merge function doesn't work. At
>really, trying to merge, if someone else skip one line or something like
the
>file corrupts.
>Due to this we have the true need to lock the files to avoid double
editing,
>or else we will lost our work.
>Other big problem: some notebooks here are win98 then we can't use named
>pipes (in fact we don't have this protocol here).
>
>I am trying to use the cvs in pserver mode but when I try to lock files it
>says that this feature is reseverd to repository administrators. I searched
>over the internet/documentation for many possibilities:
>
>* create cvsadmin group and join people to this group
>* create admin file on cvsroot
>* use edit -c instead
>* etc
>
>But it only works when I grant administrative rights to the user. I can't
do
>it for everybody because this is madness. It is not safe. My network admin
>won't allow it.
>
>What can I do?
>
>Move to a unix sever?
>
>Thanks,
>
>Luis Felipe da Costa Antoniosi
>E-mail: felipe.antoniosi at sfw.com.br
>

I think you have to find yourself a different version control system.
PVCS and the other commercial ones do have locks, but they are also
expensive.
Maybe FreeVCS can be your selection? That is where I started out 16
months ago, but I switched to CVS because I liked the large community
of peers for support.
I think FreeVCS may be right for you because it stores the data not as
diffs but as complete committed files and it does not matter if it is
text or binary. I don't remember if it has a locking command though,
but you won't ever corrupt a file by setting the wrong options, I'm
sure. Here is an URL where you can start reading:
http://www.thensle.de/index.htm

/Bo


/Bo
(Bo Berglund, developer in Sweden)
_______________________________________________
Cvsnt mailing list
Cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt




_______________________________________________
Cvsnt mailing list
Cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt



More information about the cvsnt mailing list