[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: Gunter Ohrner <G.Ohrner_at_post.rwth-aachen.de>
Date: 2006-01-04 16:43:32 CET

Ryan Schmidt wrote:
>>> Is there any way to assign something like "auto-props" to a
>>> repository /
>>> subdirectory instead of a client's subversion config?
>> repository or even subdirectory-tree specific "global-ignores".

> Directory-specific "global-ignores" is what the svn:ignore property
> is for.

Mh, well, that's per-directory-ignores. I was looking for an way to set an
ignore with at least a recursive effect for all directories (even
not-yet-created) below. So this feature doesn't seem to exist yet... :-(

> it sounds like you want an automatic way to set svn:ignore on a large
> or frequently-changing set of directories;

Right. Or at least for a way to "apply" these ignores to a subtree without
even setting them everywhere recursively, like global-ignores do. (Hence my
unlucky comparison above.)

> I'm not aware of a built-in way to do that.

Recursively setting the properties is no problem, but remembering to
actually set them and keep them up-to-date is painful and error
prone... :-(

> Another problem in your case is that auto-props only works on files,

Uh, I didn't even think of that. So there's no way to automagically attach
ignores to new files/directories yet, besides custom configuration files
which do not actually put the ignores where I want them to be... :-(

>>> 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: (...)
> 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

I know this switch, but using it manually is also clumsy and error prone...

> 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.

Ok, so the summary is that there's currently no way to achieve what I want
and I'll have to stick to mainting these properties using scripts and a lot
of discipline... ;)

These would be nice features to have, and at least from the outside they
don't sound too complicated, as it'd be client-only features. I guess I'll
open wishlist-items for these.

Thanks a lot for your help,


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 4 16:56:04 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.