[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: why don't relative paths work when specifying a remote repository ?
From: |
Kaz Kylheku |
Subject: |
Re: why don't relative paths work when specifying a remote repository ? |
Date: |
Mon, 10 Nov 2003 14:07:52 -0800 (PST) |
On Mon, 10 Nov 2003, Larry Jones wrote:
> Date: Mon, 10 Nov 2003 16:42:52 -0500 (EST)
> From: Larry Jones <address@hidden>
> To: "Patton, Matthew E., CTR, OSD-PA&E" <address@hidden>
> Cc: "'address@hidden'" <address@hidden>
> Subject: Re: why don't relative paths work when specifying a remote
> repository ?
>
> Patton, Matthew E., CTR, OSD-PA&E writes:
> >
> > Why is "cvs -d address@hidden:./some_relative_path" style syntax not
> > supported?
>
> 1. Many parts of the CVS code require the root to be an absolute path
> -- allowing a relative path would require either changing all that code
> or adding code to the server to convert the relative path into an
> absolute path.
If you want to abstract the location, you can use symbolic links:
/secret-cvs-location/myproject
This is semantically as good as
./myproject
The /secret-cvs-location component is a symbolic link from the root
directory to wherever you want. If you need to move the repository,
you adjust the symbolic link.