As Andy Levy stated, there is no global setting for auto-props.
However, if you provide a standard Subversion config file in a place
where developers can grab it (like the company Wiki), and you use
trigger scripts to enforce the property settings, your developers will
quickly learn to set auto-props themselves. It would be nice to have a
global setting, but I can tell you from experience that a pre-commit
trigger works pretty well.
I don't know if the standard Python pre-commit access control hook can
verify that properties are set or not. You should check that one first
since it's the standard Subversion pre-commit trigger. However, if
that one doesn't check properties,, I have my own Perl version that
does verify that particular properties are set and that they have the
correct value. It can be found at
<http://dl.getdropbox.com/u/433257/hooks.zip>.
On Thu, Apr 9, 2009 at 12:56 PM, DW Dennis Wheeler <dwheeler_at_ag.com> wrote:
> I searched the docs and web and have so far been unable to find a clear
> answer.
>
> I see that enabling auto-props in one's local client will set the
> appropriately defined properties for some defined fileset for newly
> added files -- but that's only local to that one user.
>
> How do I set that globally for all users?
>
> Can I simply copy the same settings from my ~/.subversion/config into
> the server's conf/svnserve.conf file?
>
> for example:
> -----------
> [miscellany]
> enable-auto-props = yes
> [auto-props]
> *.sql = svn:keywords=Revision
>
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1617688
>
> To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
>
--
David Weintraub
qazwart_at_gmail.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1681208
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-04-13 05:20:56 CEST