Skylar Thompson wrote on Tue, Jun 05, 2012 at 21:37:30 -0700:
> On 06/05/12 18:07, Nico Kadel-Garcia wrote:
> >
> > On Tue, Jun 5, 2012 at 8:54 AM, Daniel Shahaf <d...@daniel.shahaf.name
> > <mailto:d...@daniel.shahaf.name>> wrote:
> >
> > Stefan Sperling wrote on Mon, Jun 04, 2012 at 14:52:59 +0200:
> > > On Mon, Jun 04, 2012 at 05:50:11AM -0700, Skylar Thompson wrote:
> > > > It looks like ages ago I added an svn:keywords line in the
> > autoprop
> > > > section of ~/.subversion/config and had since forgotten about it.
> > >
> > > Ah, that explains it. Thanks!
> >
> > Should we patch the reproduction template to account for this, then?
> >
> > Index: publish/docs/community-guide/repro-template.sh
> > ===================================================================
> > --- publish/docs/community-guide/repro-template.sh (revision
> > 1339099)
> > +++ publish/docs/community-guide/repro-template.sh (working copy)
> > @@ -22,6 +22,11 @@
> > SVNADMIN=`which svnadmin`
> > fi
> >
> > +# Make sure we don't use $HOME/.subversion/.
> > +SVN="${SVN} --config-dir=./svn-repro-config-dir"
> > +SVNADMIN="${SVNADMIN} --config-dir=./svn-repro-config-dir"
> > +SVNSERVE="${SVNSERVE} --config-dir=./svn-repro-config-dir"
> > +
> > # Use English output.
> > LC_ALL=C; export LC_ALL
> >
> >
> > (Ideally we would have "--no-config-dir" of some sort, but the above
> > works with existing released code
> >
> >
> >
> > I'd like to put a big vote up for "--no-config-dir" When verifying a
> > new user's account against a common repository, I *do not want*
> > Subversion to check against or touch my existing $HOME/.subversion, or
> > anyone else's. It would be particularly useful for the Nagios
> > "check_svn" utility, where using saved configurations would conflict
> > with the command line operations and potentially provide the "nagios"
> > user..... inappropriate access to the tested repository on an ongoing
> > basis.
> I'll throw another +1 in on this too. Out of curiosity, is there a
Can someone file a feature request in the issue tracker, please? (and
CC 'danielsh')
Patches would be welcome as well. The starting point is
subversion/svn/main.c, but I don't recall offhand whether any public
APIs would need to be rev'd.
> debug/verbose mode for svn that reveals where options are coming from?
>
No, but there are exactly 5 places:
- system-wide registry (windows only)
- /etc/subversion
- user's registry (windows only)
- ${CONFIG_DIR:-$HOME}/.subversion
- --config-option (and similar) on the command-line
> Skylar
