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

Re: override global-ignores from server side

From: Johan Corveleyn <jcorvel_at_gmail.com>
Date: Tue, 26 Sep 2017 02:37:23 +0200

On Tue, Sep 19, 2017 at 4:21 PM, Branko Čibej <brane_at_apache.org> wrote:
> On 19.09.2017 11:02, Bert Huijben wrote:
>>
>>> -----Original Message-----
>>> From: Balogh Péter [mailto:balogh.peter_at_xcite.hu]
>>> Sent: dinsdag 19 september 2017 10:59
>>> To: users_at_subversion.apache.org
>>> Subject: Re: override global-ignores from server side
>>>
>>> Hi,
>>>
>>> Yes, I'm aware that adding the .a file manually is possible, but it does not
>>> solve the issue, that 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
>> Where I work we have a strict policy that we don't release binaries that are built on normal workstations, just those on regulated build systems where we can 100% reproduce previous builds. Having a default that would make users commit locally build artifacts would go against that. We manage these artifacts using different tooling that was designed for that purpose.
>
> Well frankly I was under the impression that svn:global-ignores overrode
> the global-ignores client config setting. Apparently it does not ... I'd
> call that a bug, but that's water under the bridge ...
>
> -- Brane

Indeed, the designed behaviour (IIUC) was definitely that the
repository-dictated configuration would take priority over the
client's config setting [1] (except for command-line options, which
take even higher priority, as discussed / clarified here: [2]).

The OP has created a JIRA issue:
https://issues.apache.org/jira/browse/SVN-4699

I'll add these references also to that issue.

(Note to Peter Balogh: having the issue in JIRA does not mean it will
be solved more quickly -- someone still needs to pick it up,
investigate, discuss, and possibly come up with a patch -- any further
help there is most welcome :-))

[1] https://wiki.apache.org/subversion/ServerDictatedConfiguration#Configuration_hierarchy

[2] https://svn.haxx.se/dev/archive-2012-01/0210.shtml

-- 
Johan
Received on 2017-09-26 02:37:47 CEST

This is an archived mail posted to the Subversion Users mailing list.