On Wednesday, February 23, "Noel L Yap" wrote:
> >
> >But note that there *isn't* a per-filesystem .profile, which is
> >essentially what people are asking for from cvs. I wouldn't have a
> >problem with a *system* preferences file ala /etc/profile, but I
> >strongly object to a per-repository preferences file. I don't know
> >about you, but *I* certainly don't want diff to behave differently just
> >because I'm working in a different directory, nor do I want cvs to work
> >differently just because I'm working in a different repository.
>
> System-wide preferences would have to exist on the same machine as the binary.
> So now, instead of "cvs diff" working differently from one directory to
> another, it would work differently depending on which server the repository
> resides. It would also mean that, if one were to move the repository, the
> behaviour of commands would change.
This behavior change is exactly what people are opposing to. If it comes
out of 2 different repos (yes, there are those of us who work on 2 or more
different CVS repos!), or from using 2 different machines...
> As for commands working differently from one directory to another. The
> original post regarded a per-repo CVSROOT/cvsrc file. I did mention
> possibly having per-module .cvsrc files, but I don't consider it necessary
> and, I haven't thought too much about it to deem it not dangerous.
Yes, per-repo, but, again, some of us use different repos...
> Also, the admin (and the team) should be sure to place only "good" things
> within the global defaults file (just as they do now with CVSROOT/config).
> Furthermore, users should be able to override the global settings.
Same as they can do now...
--Toby.
