Re: [Mod-security-developers] Autotools results shouldn't be in the SCM

[Diego E. P. <fla...@gm...>]

Il giorno mar, 19/04/2011 alle 11.30 -0500, Breno Silva ha scritto:
> 
> What files are creating this problem ? 

#	modified:   Makefile
#	modified:   Makefile.in
#	typechange: acinclude/libtool.m4
#	typechange: acinclude/ltoptions.m4
#	typechange: acinclude/ltsugar.m4
#	typechange: acinclude/ltversion.m4
#	typechange: acinclude/lt~obsolete.m4
#	modified:   aclocal.m4
#	modified:   alp2/Makefile.in
#	modified:   apache2/Makefile
#	modified:   apache2/Makefile.in
#	modified:   autom4te.cache/output.0
#	modified:   autom4te.cache/output.1
#	modified:   autom4te.cache/requests
#	modified:   autom4te.cache/traces.0
#	modified:   autom4te.cache/traces.1
#	typechange: build/config.guess
#	typechange: build/config.sub
#	typechange: build/depcomp
#	modified:   build/find_lua.m4
#	typechange: build/install-sh
#	typechange: build/ltmain.sh
#	typechange: build/missing
#	modified:   config.log
#	modified:   config.status
#	modified:   configure
#	modified:   ext/Makefile.in
#	modified:   libtool
#	modified:   mlogc/Makefile.in
#	modified:   tests/Makefile.in
#	modified:   tools/Makefile.in

In this list the one file I modified was build/find_lua.m4, the rest are
re-generated by autotools. In particular autom4te.cache is totally
useless (it's a temporary cache that depends per-system); Makefile.in
are generated by automake, config.log by ./configure and so on so forth.

-- 
Diego Elio Pettenò — Flameeyes
http://blog.flameeyes.eu/