1.6.15 failure of svnlook_tests.py 11

2010-12-23 Thread tsteven4
When I run "./svnlook_tests.py 11" the test passes, but when I pass the url of an apache server such as "./svnlook_tests.py --url http://server 11" or "./svnlook_tests.py BASE_URL=http://server 11" it fails. I am running Oracle Solaris 10 9/10 s10s_u9wos_14a SPARC. Normally I pass url paramet

Re: --no-config-dir option?

2010-12-23 Thread Les Mikesell
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

Re: --no-config-dir option?

2010-12-23 Thread Alan Barrett
On Thu, 23 Dec 2010, Stefan Sperling wrote: > You could [do this or that] Sure, I can easily make svn create the .subversion directory elsewhere, in a number of ways, but I don't want to have it at all. > That said, I don't see an issue with adding the option you're asking for. > It is a reasonab

Re: --no-config-dir option?

2010-12-23 Thread Stefan Sperling
On Thu, Dec 23, 2010 at 10:56:17AM -0600, Les Mikesell wrote: > On 12/23/2010 10:24 AM, Stefan Sperling wrote: > > > >>If you don't need to write/modify something there, why should it be > >>created if it doesn't already exist? Can't you defer the decision > >>to create until you need a write? > >

Re: --no-config-dir option?

2010-12-23 Thread Les Mikesell
On 12/23/2010 10:24 AM, Stefan Sperling wrote: If you don't need to write/modify something there, why should it be created if it doesn't already exist? Can't you defer the decision to create until you need a write? That would mean going into the code of each operation within libsvn_client an

Re: --no-config-dir option?

2010-12-23 Thread Stefan Sperling
On Thu, Dec 23, 2010 at 10:09:23AM -0600, Les Mikesell wrote: > On 12/23/2010 9:56 AM, Stefan Sperling wrote: > > > > > >Yes, every svn subcommand creates it, and it has been pointed out before > >that this might not be necessary. > >However, I'm wondering if it's even possible to come up with a go

Re: --no-config-dir option?

2010-12-23 Thread Daniel Shahaf
Alan Barrett wrote on Thu, Dec 23, 2010 at 17:34:09 +0200: > On Thu, 23 Dec 2010, Stefan Sperling wrote: > > I don't think there is an official way to prevent the config dir from > > being created. I'd be interested to know why you need this. What is > > your use case? > > The event that made me n

Re: --no-config-dir option?

2010-12-23 Thread Les Mikesell
On 12/23/2010 9:56 AM, Stefan Sperling wrote: Yes, every svn subcommand creates it, and it has been pointed out before that this might not be necessary. However, I'm wondering if it's even possible to come up with a good split between subcommands that should create it and ones that shouldn't.

Re: --no-config-dir option?

2010-12-23 Thread Stefan Sperling
On Thu, Dec 23, 2010 at 05:34:09PM +0200, Alan Barrett wrote: > On Thu, 23 Dec 2010, Stefan Sperling wrote: > > I don't think there is an official way to prevent the config dir from > > being created. I'd be interested to know why you need this. What is > > your use case? > > The event that made m

Re: --no-config-dir option?

2010-12-23 Thread Alan Barrett
On Thu, 23 Dec 2010, Stefan Sperling wrote: > I don't think there is an official way to prevent the config dir from > being created. I'd be interested to know why you need this. What is > your use case? The event that made me notice the problem was cron job owned by root, whose command was somethi

Re: --no-config-dir option?

2010-12-23 Thread Ryan Schmidt
On Dec 23, 2010, at 09:16, Eric Hudish wrote: > See: > Let's not refer people to the old Subversion 1.1 book anymore. The link to the current version of that page (currently for Subversion 1.6) is: http://svnbook.red-bean.com/nigh

Re: --no-config-dir option?

2010-12-23 Thread Eric Hudish
On Thu, 2010-12-23 at 16:54 +0200, Alan Barrett wrote: > Is there a way to prevent svn from creating a $HOME/.subversion > directory? I know how to make it put the directory in a different > location using --config-dir=/wherever, but I want to avoid creating > it entirely. I can't find an option

Re: --no-config-dir option?

2010-12-23 Thread Stefan Sperling
On Thu, Dec 23, 2010 at 04:54:27PM +0200, Alan Barrett wrote: > Is there a way to prevent svn from creating a $HOME/.subversion > directory? I know how to make it put the directory in a different > location using --config-dir=/wherever, but I want to avoid creating > it entirely. I can't find an

--no-config-dir option?

2010-12-23 Thread Alan Barrett
Is there a way to prevent svn from creating a $HOME/.subversion directory? I know how to make it put the directory in a different location using --config-dir=/wherever, but I want to avoid creating it entirely. I can't find an option like "--no-config-dir" or "--config-dir=none". I have discover