Re: using cvschroot allowed?

[Harald Dunkel]

Hi Mark,

Mark D. Baushke wrote:
> Harald Dunkel <harald@CoWare.com> writes:
> 
> 
>>> Question: Is it allowed to use cvschroot in this way? Or is
>>> this too much of a hack, maybe corrupting my CVS repository
>>> at checkin? Anything I should take into account to make this
>>> work?
> 
> Well, I would try to avoid excessive use of this technique as an
> interruption during the altering of the CVS/Root process might leave
> your tree in an odd state.
> 

I see. So either it should be made very hard to interrupt cvschroot,
or I should explicitly use 'cvs -d $CVSROOT_WRITEABLE commit', etc.
instead, since setting $CVSROOT is not sufficient to override CVS/Root.

> 
> Please note that there are two separate methods available to have a
> read-only CVS repository that may be used for checkout and without any
> changes to the user's workspace.
> 
>   1) Allow a commit via a writeproxy configuration (needs cvs 1.12.x
>      where x > 9). Note: Not many folks are using this feature right
>      now.
> 

Its been some time since I looked at this feature, but AFAIR it did
not support pserver, and the documentation about setting the
scripting hooks and the necessary file system locks was a little
bit "thin".

>   2) Use a commercial product add-on to CVS from WANdisco.com
> 

Of course there are many commercial version control systems available,
but lets assume that this is not an option.

> You may find doing a goole for 'cvs multisite' and 'cvs writeproxy' may
> be useful to you.
> 

I will check. Many thanx


Harri