Re: Issue 1538 -- local path style

Philip Martin wrote:
> Julian Foad <julianfoad@btopenworld.com> writes:
>
>>* Make it absolute, so that the user can find it without having to
>>know or guess what the current working directory was at the time.
>
> I don't like that idea.

I should have stated explicitly: I started working on this because at least two people asked on the list about an error thrown by mod-dav-svn about "cannot create temporary file 'blah'" and it was not at all obvious where or why, because the users did not know what the current working directory was of that module running on their server. (Of course a sysadmin should know and should be able to find out, but that's beside the point. Perhaps someone runs 'svn' in lots of different directories within a Unix 'find' command, etc.)

> - If I supply relative paths to a command, as I usually do, I expect
> relative paths in the error messages.

Granted.

> - If Subversion is working with relative paths internally, as it
> usually does, then converting to absolute paths can make bugs
> harder to diagnose.

Granted.

> - Symbolic links mean that the absolute path you choose may not be
> the absolute path preferred by the user.

Granted.

> - Absolute paths make the error messages longer.

Granted.

Looks like we'd want it relative as a first stab, and perhaps configurable to absolute as a later enhancement.

- Julian

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 25 02:08:07 2003