On Wednesday, February 23, "Noel L Yap" wrote:
>
> This is not a communication issue. It's a configuration issue. CVS should
> have a way to set default configurations (at least per repo or possibly per
> module).
Why? It does have a way to set a default "configuration", on a per-user
basis. This is not really a "configuration" per se, but a "preference"
file, which states certain preferences a user has in order to use CVS.
> Your view seems to say that there should be no such thing as /etc/profile
> for sh and that users must create there own .profile files.
Yes, I believe users should create their own .profile files. I'm in a job
right now where I do provide .profile files to people, however, they are
free to modify them as they wish. I don't dictate that they should have
a certain $PATH configuration, etc.
> Furthermore, developers already have to learn a lot in an environment. The
> less they have to know, the better they can know the rest. This means that,
> if CVSROOT/cvsrc existed, CVS procedures and default behaviours can be
> documented, but users won't have to create their own .cvsrc (unless they
> wish to extend or override the defaults).
In other words, you wish them to continue in their ignorance. That is fine,
it is one way of doing things. Another way of looking at the .cvsrc file, is
to say that the "stock" CVS binary, without a .cvsrc file, is the default
behaviour of CVS. The .cvsrc file is a local extension to override the
default behaviour... :-)
--Toby.
