On Monday, February 14, "Win32 M$" wrote:
>
> Purists? You kidding? To ignore the fact that the (BAD) locks are there you
> call purists? To be blind by the ideology (this forum is about the
> technology) is purists? Wake up, man!
The "locks" current available due to 'cvs admin', are an artifact due to the
RCS backend that CVS was first built on. CVS was meant as a tool to manage
a collection of RCS files, with certain ways of dealing with conflicts. The
'cvs admin' collection of commands were a *DIRECT* interface to the RCS backed.
One of the repeated things that keep coming up, both here on the list, and in
the manual(s) is that the RCS backend should/could be replaced sometime. Maybe
with xdelta type stuff. At that point, and maybe sooner, the 'cvs admin' hook
to the RCS locks (which 'cvs admin -l' are) will go away.
> >If your shop uses "facist" locking with CVS, then they are using it wrong.
>
> Right, but the facist locking in in CVS in the first place?
Just because there is a corkscrew on a swiss army knife, does it mean you
need to use it? Why not use the knife instead, if you wish to cut something?
I'm telling you there are better ways to handle your VB files.
> >You have such a versioning system. You describe it above. It's VSS.
>
> Or: Why not make the proper locks in CVS?
I've answered this to exhaustion...
--Toby.
