[ On Thursday, February 24, 2000 at 14:01:58 (-0500), Noel L Yap wrote: ]
> Subject: Re: CVSROOT/cvsrc
>
> Yes, this is doable. Another solution might be to checkout CVSROOT/cvsrc onto
> ~/.cvsrc via "cvs co -p CVSROOT/cvsrc > ~/.cvsrc".
That's not a very smart thing to do if you want to record preferences
within the repository. You should use a separate module and an
installation tool.
> Note that this also doesn't
> allow for user overrides or extensions (in fact, it will even wipe out any such
> user preferences).
Then don't do it. Make up your mind! :-)
> > One more time: ~/.cvsrc contains *user* preferences that have nothing
> > whatsoever to do with which repository the user is accessing (with the
> > possible exception of cvs -z). They most definitely do *not* belong in
> > the repository.
>
> I think they should be allowed to belong in the repo if this is what the team
> deems correct. "cvs -z" should definitely belong on the server since the server
> is the one that can decide best what level of compression should be used.
What don't you understand about "*user* preferences"? They have
absolutely *no* place being centrally integrated in the repository!
If you want to provide a template that can be centrally managed then
there are a zillion and one ways of doing this with CVS in a separate
module and an equally infinite number that don't use CVS. Absolutely
none of them require any integration within CVS.
--
Greg A. Woods
+1 416 218-0098 VE3TCP <[EMAIL PROTECTED]> <robohack!woods>
Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>
