[
https://issues.apache.org/jira/browse/SVN-4699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16180012#comment-16180012
]
Johan Corveleyn commented on SVN-4699:
--------------------------------------
This was discussed in this thread on users@:
https://svn.haxx.se/users/archive-2017-09/0032.shtml
It seems the repository-dictated svn:global-ignores setting does not override
the global-ignores client config setting. According to the original
specification [1] the repository-dictated setting should take priority though.
[1]
https://wiki.apache.org/subversion/ServerDictatedConfiguration#Configuration_hierarchy
(later tweaked in https://svn.haxx.se/dev/archive-2012-01/0210.shtml (giving
command-line options even higher priority))
> svn:global-ignores does not override the client config setting
> ---------------------------------------------------------------
>
> Key: SVN-4699
> URL: https://issues.apache.org/jira/browse/SVN-4699
> Project: Subversion
> Issue Type: Bug
> Reporter: Peter Balogh
>
> By default, for example the .a files are ignored in the svn clients
> Since we're developing mobile multi platform titles, it's common to add
> certain libraries as .a files to the repository
> we have to check manually after every library update, if a new .a file is
> added
> And the issue won't show up, until we commit the changes, and the CI build
> fails with a linking error
> The default list is not large, that's why overriding it does not seem to be
> an irrational request
> But right now, if I put a .a file in an SVN, I have no way to make it show up
> in the status without client side modifications, and I think it's a really
> important missing feature
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
