[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: --no-config-dir option?

From: Les Mikesell <lesmikesell_at_gmail.com>
Date: Thu, 23 Dec 2010 12:33:03 -0600

On 12/23/2010 11:37 AM, Stefan Sperling wrote:
>> Seems like it should fit in an error handler somewhere. Let the
>> write fail in the uncommon case and fix things up only when needed.
> That still means checking for this error in many places and retry.
> We have no way to jump back down to where the error was thrown,
> other than calling the error-throwing function again. If you catch
> the error at a high level this means you'd effectively have to restart
> the entire operation (like, say, "svn merge", which may or may not write
> to files and properties in the WC). So you need to catch it as early
> as possible. This means you'll have to catch it in many places.

Maybe it would have had to be designed in from the start.

> Maybe there really is a good way of doing what you'd like to do,
> but I don't see how. You could try to have a look into the code
> yourself to see if you can find a way to do it. I suppose it also
> depends on what you would call a "write" operation in this context.
> Does creating temporary files count, for example?

That would depend on whether they have to be in $HOME/.subversion or
not. Other programs generally use $TMPDIR for scratch space but it is
always dangerous to change an existing program's behavior.

   Les Mikesell
Received on 2010-12-23 19:33:45 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.