[EMAIL PROTECTED] on 2000.02.23 16:37:43
>Noel L Yap <[EMAIL PROTECTED]> on 02/23/2000 09:33:02 AM
>>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).
>
>In order to implement this there is only two options that I can see.
>either the client will have to connect to the host to get this repo
>config file for all commands, which is unacceptable in many peoples
>view, or the config file will have to be stored in each CVS directory in
>the sandbox, which isnt very nice either.
What's wrong with the latter solution. CVS already does this for some things.
>>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.
>
>many of the unix systems I administered in the past did not have this
>feature. This didnt stop the users from getting their job done.
Of course users were still able to perform their jobs. The issue is not
necessity, but nicety ;-)
>Most of the argument centers around a few options I think, and some,
>including me would probably be satisfied if -PAd were the default
>on update.
I don't think -A should be part of the default to "cvs up" unless there's a way
to override it. Even then, I'd probably vote not to have it automatically
unsticky anything.
OTOH, -A is one of the things that my team has voted to place in the global
defaults. Since I don't like this, I maintain my own ~/.cvsrc file. This is
the reason why, if CVSROOT/cvsrc were added, there should be a way to extend
and/or override the settings.
Noel
