[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

why don't relative paths work when specifying a remote repository ?

From: Patton, Matthew E., CTR, OSD-PA&E
Subject: why don't relative paths work when specifying a remote repository ?
Date: Mon, 10 Nov 2003 14:38:36 -0500

Classification: UNCLASSIFIED

I didn't see anything in the archives when I searched around.
I'm running in client-server mode over ssh and I have multiple cvs trees
with their respective user communities and CVSROOT's hosted on the same
server and within the same filesystem structure: ie /var/cvs/...

I would like to just give my users a relative path to specify with '-d' or
with CVS_SERVER variables but apparently cvs doesn't like that and taunts me
with messages like "did you try to use a relative path"? Why do I want to do
this? So that if I choose to move the trees around it is totally transparent
to the users. And furthermore to prevent some level of intelligence
gathering by the users. The file permissions are heavily restricted as is
but since the files are often somewhat important (system configurations) I
want to keep the nefarious activity down between the parties.

Why is "cvs -d address@hidden:./some_relative_path" style syntax not supported?
When going over ssh in CS mode the CWD is the user's home directory or since
I'm actually using a wrapper shell script, a directory somewhere in the cvs
hierarchy before 'cvs server' is even invoked. How come CVS won't just treat
specified paths as being relative to CWD?

I don't have source yet but am I missing something important by planning to
just yank the offending "nanny" code?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]