[EMAIL PROTECTED] on 2000.02.23 14:33:37
>Per-site config (say, /etc/cvsrc) will be fine with me. BTW, it could also
>contain allowed roots thus solving the problem with braindead inetd in a
>clear and elegant way.
/etc/cvsrc is OK by me, but CVSROOT/cvsrc is more preferable. Some of the
drawbacks with /etc/cvsrc are:
1. Defaults depend on which server the repo resides. If the repo is moved, the
defaults may change.
2. /etc/cvsrc depends on sysadmin access. Some sites, including my own, don't
have easy sysadmin access -- it'd be much easier to change something in the repo
than something in /etc.
Some of the benefits of CVSROOT/cvsrc are:
1. Each project may set their own defaults if they each have their own
repositories.
2. None of the drawbacks mentioned above.
Therefore, I won't fight against /etc/cvsrc (I just won't use it), but I will
fight for CVSROOT/cvsrc.
Now, I know the above list is biased, so I'd appreciate someone else giving some
balance to those views.
Noel
