On 19.09.2017 11:02, Bert Huijben wrote: > >> -----Original Message----- >> From: Balogh Péter [mailto:balogh.pe...@xcite.hu] >> Sent: dinsdag 19 september 2017 10:59 >> To: users@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
