[darcs-devel] [issue595] get to remote repo fails when upstream directory permisions are restrictive

[David Roundy]

I'm skeptical of this bug.  Is it really not a broken system if we cannot chdir
into the repository directory? It's possible to fix this by only using relative
paths, but the reason we preferentially use absolute paths is because the use of
relative paths tends to be fragile, in the sense that they can easily lead to
bugs when small changes are made to the code.

A related question:  does situation invalidate *all* uses of absolute paths, or
only for certain operations like chdir? The only even moderately robust solution
I can imagine would be to replace all uses of setCurrentDirectory (and perhaps
all other FS access routines?) with one that checks the current directory and
computes from it a relative path to the absolute path we want to access.  It
sounds very fragile, and I'd really prefer not to take this approach.

So my leaning for this scenario would be to instruct users to run darcs in a
directory they have permissions to access with an absolute path.

----------
nosy: +darcs-devel, jch
status: unread -> chatting

__________________________________
Darcs bug tracker <bugs at darcs.net>
<http://bugs.darcs.net/issue595>
__________________________________