The solution to the locking problem would be to set LockDir within
CVSROOT/config.
If you want finer-grained permissioning (eg some people are trusted only to some
modules), look into using AFS ACLs (I'm assuming they exist).
Noel
[EMAIL PROTECTED] on 05/28/2000 06:10:15 AM
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc: (bcc: Noel L Yap)
Subject: CVS with AFS: optimal permissions?
Hello!
I am trying to use CVS where the repository resides on AFS.
I want to make everyone able to check out the files,
but only trusted people to check in.
However, people without write access can not check out
files because CVS is unable to lock the repository.
this happends with any version of CVS.
The problem is that AFS only allow permission control per directory.
1. Did anyone around there did anything like that in the past?
2. Is there an option for CVS to go ahead and get the file
without locking (suppress the error message)?
The inconsistency problem could be solved by the client
by re-checking the file after it is checked out, and making sure
that no changes were done.
thanks,
mst
--
This message content is not part of Intel's views or affairs
Michael S. Tsirkin
> Four things are to be strengthened: Torah,and good deeds,
> prayer and one's good manners (Berachoth)
This communication is for informational purposes only. It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan & Co. Incorporated, its
subsidiaries and affiliates.
