Post by Victor PortonWhich of the following files should be uploaded to Git?
It depends. Do you want git to track generated files, at the risk of
different installed autotools versions creating spurious diffs in those
generated files? I don't personally recommend that, but some people
like to have their git repo usable even by someone that does not have
the autotools installed. Or do you want to require someone checking out
the git repo to have tools installed on their machine that the end user
client of a tarball does not have to have?
Generated.
Not necessarily the best name (since there is an unrelated GNU Autogen
project); some projects prefer the name bootstrap for this sort of
script instead of autogen.sh. At any rate, this script is NOT generated
by the autotools, so you probably need to check it into git (especially
if its goal is to run the autotools to bring a git checkout into a state
that you can then run the usual ./configure && make).
Post by Victor Portoncompile
config.guess
config.sub
configure
depcomp
All generated.
If you don't check this in, then you get the default version generated
that talks about GNU standards. Which may be fine for your project, or
it may be inaccurate; if you check in your own version, automake will
leave your version intact.
Post by Victor Portoninstall-sh
libtool
ltmain.sh
missing
All Generated.
So of those, I'd only check in autogen.sh (and consider renaming it).
However, your subject line said "Which files to distribute", not "Which
files to store in version control". The answer there is "All of them" -
and automake will automatically distribute all of those files in a
tarball when you do 'make dist' (and you can run 'make distcheck' to
make sure your tarball is self-contained).
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org