tagged version vs released tarball

Dmitry V. Levin ldv at altlinux.org
Mon Mar 12 21:17:17 UTC 2012

On Mon, Mar 12, 2012 at 08:50:44PM +0100, Abdoulaye Walsimou GAYE wrote:
> Sorry for this thread hijack,

Could you at least change the subject next time, please?  Thanks.

> but I noticed that tagged version and corresponding
> tarball does not contain the same files. This prevents for example to cherry-pick
> some critical fixes and apply them against the release tarball source code, if you
> don't want to wait several months for a new release.
> So it would nice to to release a tarball which contains the same files as the tag.

Released tarballs are produced by "make-dist" script, which essentially does
"autoreconf -f", "configure --enable-maintainer-mode" and "make distcheck",
which in turn pack some additional autotools- and git-generated files, and
leave some git-only files out.

There should be no problem to build strace from a git checkout, just have
a look at "make-dist" script.  "autoreconf -if && ./configure && make"
should be enough in most cases.  One can expect that HEAD always builds
and works at least on x86-64.

Said that, we probably should consider releasing strace more often.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.strace.io/pipermail/strace-devel/attachments/20120313/ee58a6e0/attachment.bin>

More information about the Strace-devel mailing list