Untrack and ignore generated files

[GoogleCodeExporter]

Many generated files are currently tracked under Git, which is not useful 
(since they are generated automatically) and may be annoying if the user's 
tools generates them differently (like a different Autoconf or Automake 
version).  

Attached is a patch that untracks them and makes Git ignore them.

Original issue reported on code.google.com by colomb4n on 24 Apr 2012 at 6:42

Attachments:

• 0001-Untrack-and-ignore-generated-files.patch

[GoogleCodeExporter]

I prefer to leave these tracked in git so that anyone can build from
the git source without having to install the requisite tools.

This can be challenging if one doesn't have root on the build machine and
the tools either aren't installed or aren't at a compatible version level.
(Think AIX, Solaris, HP-UX).

Original comment by garlick....@gmail.com on 24 Apr 2012 at 8:15

[GoogleCodeExporter]

This is generally addressed by providing tarballs (created by make dist), maybe 
nightly tarballs if a bleeding-edge version is important.

The reason I initially reported this and created the patch is that the version 
of the tools I have generates different outputs for many files (Makefile.ins, 
configure, etc.) and it is then harder to deal with the repository since there 
are changes that should not be committed, and that may theoretically create 
conflict when e.g. switching branches.

However if you think it's better as it is now, I won't make noise any further :)

Original comment by colomb4n on 24 Apr 2012 at 8:24

[GoogleCodeExporter]

I'm inclined to leave things as they are, although I'll leave this bug open for 
now and think about it.

Original comment by garlick....@gmail.com on 24 Apr 2012 at 8:45

[GoogleCodeExporter]

I've come around to your way of thinking.  This will be fixed in the next 
release.

Original comment by garlick....@gmail.com on 18 Aug 2014 at 11:10

• Changed state: Fixed