Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Subject: Re: override global-ignores from server side
To: users@subversion.apache.org
References: <2c62dd5c-7185-7284-3b71-30f5505adda3@xcite.hu>
 <015b01d33124$f51f76e0$df5e64a0$@qqmail.nl>
 <d5885fbb-4b6b-a8a9-8c61-37450c48db5b@xcite.hu>
 <016401d33126$15b184b0$41148e10$@qqmail.nl>
From: =?UTF-8?Q?Branko_=c4=8cibej?= <brane@apache.org>
Organization: The Apache Software Foundation
Message-ID: <f732dcc0-6efc-e31f-7612-18a2ec2def65@apache.org>
Date: Tue, 19 Sep 2017 16:21:26 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0)
 Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <016401d33126$15b184b0$41148e10$@qqmail.nl>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Content-Language: en-GB
archived-at: Tue, 19 Sep 2017 14:21:33 -0000

On 19.09.2017 11:02, Bert Huijben wrote:
>
>> -----Original Message-----
>> From: Balogh Péter [mailto:balogh.peter@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