Guilhem BONNEFILLE wrote:
>
> Hi,
>
> I want to use CVS in a reserved checkout model with centralised access
> to repository. It's to say :
> - reserved checkout : developpers need to lock files before act ;
The best you're going to do is cvs watch and cvs edit, particularly
with Noel Yap's patches. Actual locking is not well supported, and
what support there is may go away.
cvs edit, when properly used, gives you every benefit you would get
from locking.
> - centralised access : developpers only have read acces to repository.
> They need to send their modified files to a configuration manager
> (human) which is able to commit works.
>
Possibly you could use commitinfo or something like that, or use
directory permissions.
> It's a non natural model for CVS, but it's a model I need to use.
>
Why? If you don't trust your developers, fire them and hire new ones.
If you do trust them, establish procedures that work, and tell them
to follow them. The reason why it's unnatural for CVS is that it's
unnatural for software development in general.
You have to trust your developers to be working for you, not against
you; there's too many things they can do if they don't like you
that the configuration manager is not going to catch.
If this is a management requirement, then you will have to treat it
like any other case of irrational management: tell them what they
want to hear, live with stupidity, change jobs, whatever.
--
David H. Thornley Software Engineer
at CES International, Inc.: [EMAIL PROTECTED] or (763)-694-2556
at home: (612)-623-0552 or [EMAIL PROTECTED] or
http://www.visi.com/~thornley/david/
