2

Is it possible to somehow override default algorithm for assigning SVN properties using the svn:auto-props? (Obviously only for those that do use svn:auto-props...)

In particular how do I assure that svn:executable is not set based on corresponding permission flag? Since default automatic properties assignment will look at the executable permission flag and if it is set it will assign svn:executable. While I would like to automatically assign this flag only to files explicitly listed in svn:executable. (Obviously user will still be able to set the property manually skipping any default algorithm.)

Adam Badura
  • 5,069
  • 1
  • 35
  • 70
  • Do you ask about `svn:auto-props` versioned property (requires SVN 1.8+ client) or about similar client runtime configuration section [auto-props]? – bahrep Jul 31 '14 at 14:03
  • I meant versioned property. That is why I named it `svn:auto-props` not `[auto-props]` ;). – Adam Badura Jul 31 '14 at 17:08

1 Answers1

1

AFAIK, svn:auto-props in SVN 1.8 does not cover such case (at least the way how I understood your case, i.e. some elaboration on your question would make it clearer). In can only set a property based on the specified pattern, it can't deny setting a property on some specific working copy items.

In other words, if you specify a pattern, those items in your WC that match the pattern will definitely get svn:executable applied.

bahrep
  • 29,961
  • 12
  • 103
  • 150
  • Even if I would include a match for everything (`*`) that would not list `svn:executable` it would still be set for files with corresponging permissions flag? (Disregarding that such a match causes other issues.) – Adam Badura Jul 31 '14 at 17:21
  • It will be set on ALL file, i.e. it will propagate downlevel on items matching `*` pattern. In case of `*` on all files. – bahrep Jul 31 '14 at 18:06
  • But what will be set? If I will make something like: `* = svn:mime-type=text/plain` then every single file will get such `svn:mime-type` property (assuming clients will honor `svn:auto-props`!). But will also every file not have `svn:executable` set automatically? Or will still files with executable bit permission have that property set? – Adam Badura Jul 31 '14 at 20:16