Hello, Larry!
> > Is there any way to manage options normally stored in ~/.cvsrc on
> > system-wide or repository-wide level?
>
> I don't understand why you'd want to do that -- essentially all of the
> stuff in ~/.cvsrc affects how the cvs commands behave and that is
> properly up to the user, not the repository administrator.
Such options as "update -P" and "checkout -P" make sence for repositories
with many dead directories. Options like "diff -u" and "cvs -z3" make
sence for anonymous CVS servers. "cvs -q" may be a good idea for
repositories with huge directory trees.
In my case the problem is that I have no time to teach everybody what to
write to ~/.cvsrc
Another solution would be to replace CVS with a hacked version using
another file in place of ~/.cvsrc
Or I could write a script checking whether ~/.cvsrc exists or not. If it
doesn't, a modified version would be executed.
But this is ugly and restricted to one machine.
Anyway, thank you for your prompt response.
Pavel Roskin
