[EMAIL PROTECTED] on 2000.02.23 13:14:22
>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.
But not on a per-repo basis (which is the topic at hand).
> This is not really a "configuration" per se, but a "preference"
>file, which states certain preferences a user has in order to use CVS.
Whether you call it preference or configuration, the team (via the admin) should
be able to set default preferences or configuration.
Of course, I see no difference between having a CVSROOT/cvsrc file and extending
the CVSROOT/config file to support repo defaults.
>> 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.
I, too, believe this, but I don't want to get into a crusade.
You haven't addressed the issue of /etc/profile, though. Does your site have an
/etc/profile? If security is such a concern, shouldn't the /etc/profile have
lines like "umask 027"? Or do you lean towards current insecure default
installations that require users to know everything in order to secure the
system?
>> 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... :-)
There are currently several default CVS behaviours:
1. Compile-time defaults via the binary.
2. Repo defaults via CVSROOT/config.
3. User-specific defaults via ~/.cvsrc
The problem is that the set of attributes controlled by CVSROOT/config is not
the same set as that controlled by ~/.cvsrc. So, since a repo default file
already exists, there should be no problem extending the concept to cover other
attributes (or, if you wish, we can call it CVSROOT/pref (or CVSROOT/cvsrc as it
originated) ;-)
Noel
