RE: default ignores
From: James French <James.French_at_naturalmotion.com>
Date: Tue, 17 Apr 2012 19:08:31 +0100
On Tue, Apr 17, 2012 at 10:18 AM, James French <James.French_at_naturalmotion.com> wrote:
I'd argue that it would be much worse to automatically include common build results for the bazillion commits that don't want them than to have to explicitly mention them in the one commit where you might. I might change my mind about that if subversion ever adds a reasonable way to remove something from a repository, but that seems more and more unlikely.
Defaults aren't ever going to suit everyone. Change them if you don't
Yeah, I think the best is a centrally manageable but user overridable system.
I would say that it is up to the user to check their commit and if it contains unwanted files then that fact should be visible to them and they can un-add them and set up an ignore if appropriate. Silently failing to add important files I think is worse because you simply don't know that its happened until something goes wrong later. I still believe that svn is a source control system that each user must take responsibility for and configure how they want. I don't think that config decisions should be taken by the core product. What if a '.a' file means something else on a different platform? Its the arbitrary nature of the excludes I don't like either (ie primarily supports the svn dev's main platform).
One could organise it so the build trees are separate to source trees which completely gets round the problem of accidentally checking in object files... This is what I've got but I'm being penalised because other people mix their build output files in with their source.
One last point is that svn is about much more than just source code these days so these default ignores just seem a bit outdated now to me.
This is an archived mail posted to the Subversion Users mailing list.