Generated files in tarball

[David Banks]

Hi all,

Mosh 0.2.6 was released with some generated files from the configure
script still in the source tarball... This can be annoying when
trying to package it for Linux distributions etc. (it means the 'make
distclean' target doesn't bring the working directory back to the same
state as the original tarball.) Can those files be excluded when
0.2.7 is released?

For reference the ones that were in the 0.2.6 tarball are:

doc/text/Download.txt
gc-7.1/bdw-gc.pc
gc-7.1/libatomic_ops-1.2/autom4te.cache/output.0
gc-7.1/libatomic_ops-1.2/autom4te.cache/output.1
gc-7.1/libatomic_ops-1.2/autom4te.cache/requests
gc-7.1/libatomic_ops-1.2/autom4te.cache/traces.0
gc-7.1/libatomic_ops-1.2/autom4te.cache/traces.1
gc-7.1/libatomic_ops-1.2/src/atomic_ops/sysdeps/gcc/x86.h.orig
lib/mosh/config.ss
lib/mosh/mysql.ss
misc/bench/TAGS
misc/example/TAGS
src/config.h.in~
src/ffitest.o
src/mosh_config
src/stamp-h1

Cheers!
--
David Banks  <amo...@gmail.com>

[okuoku]

2011/5/11 David Banks <amo...@gmail.com>:
- snip -

> Can those files be excluded when
> 0.2.7 is released?

Why not? I'm working on it :)

But we don't support "make distclean" because out-of-source build is
much more reliable and it doesn't need successful configuration.