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

Re: per-repository auto-props?

From: Ryan Schmidt <subversion-2006Q1_at_ryandesign.com>
Date: 2006-01-04 14:13:06 CET

On Jan 4, 2006, at 11:19, Gunter Ohrner wrote:

> On Jan 4, 2006, at 11:13, Gunter Ohrner wrote:
>> Is there any way to assign something like "auto-props" to a
>> repository /
>> subdirectory instead of a client's subversion config?
>> Some properties like svn:ignore contain quite a few project-
>> specific parts
>> which I a) don't want to set manually on all related clients if it
>> can be
>> avoided and b) which should only influence a subset of this client's
>> working copies.
> Also nice for similar reasons as stated above would eg. be
> repository or even subdirectory-tree specific "global-ignores".

Directory-specific "global-ignores" is what the svn:ignore property
is for. You set it on the directories where you want it to apply. But
it sounds like you want an automatic way to set svn:ignore on a large
or frequently-changing set of directories; I'm not aware of a built-
in way to do that. TortoiseSVN, for comparison, has a way to
recursively set properties, but as soon as you add new directories,
they of course won't have the property set.

Another problem in your case is that auto-props only works on files,
but svn:ignore is something that needs to be set on directories, so
auto-props doesn't work for that purpose. See this bug:


>> If this isn't possible, a (much less elegant) work around would be
>> to create
>> separate config files for these repositories. If this would be
>> neccessary,
>> is there any way to associate a specific config file with a
>> working copy?

There is the --config-dir argument to svn. From the help pages:

   --config-dir arg : read user configuration files from
directory ARG

However, you would have to give the argument every time you call the
svn program when you want to use that config directory. There's no
way to associate a config file with a given working copy or repository.

>> And does svn's config support some kind of "include" directive so
>> I can
>> define common options in a single place?

I'm not aware of any such mechanism.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 4 14:21:12 2006

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.