[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Wed, 1 Aug 2001 19:36:21 -0700
On Wed, Aug 01, 2001 at 06:50:48PM -0700, Mark D. Baushke wrote:
> Hmmm... speaking off the top of my head, perhaps something like a
> ~/.cvsrc extension that allows the transport (CVS_RSH) and remote
> operations (the CVS_SERVER and potentially other environment variables
> like CVSWRAPPER) might be interesting.
Perforce has an approach to this that might be worth investigating.
If the environment variable P4CONFIG is set, then the p4 client starts
walking up the directory tree until it finds the name pointed to by
That file will then set up appropriate variables (user name, password,
server, and so on).
CVS currently takes the approach of placing the same data into either
.cvspass or CVS/* files.
I suppose cvs COULD offer up the ability to start looking up the directory
tree for a single .cvsconfig file of some sort, and if it finds it, makes
appropriate use of it.
This would limit having to set these variables to a single file.
And, of course, this could easily be handled by a wrapper script around
cvs. Of course, since cvs is really just a wrapper script around rcs... oh
Mike Castle address@hidden www.netcom.com/~dalgoda/
We are all of us living in the shadow of Manhattan. -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); -- gcc
Re: CVS_SERVER, Mike Castle, 2001/08/01