[Debian-med-packaging] Bug#752122: Bug#752122: Patch for idba to build with clang compiler (Was: Bug#752122: idba: FTBFS with clang instead of gcc)

[Charles Plessy]

Le Fri, Jun 20, 2014 at 03:33:23PM -0700, Yu PENG a écrit :
> Here is the problem I have: I use auto tool (autoconf, automake, configure
> and make dist-gzip) to generate the distribution tarball. All Makefile and
> Makefile.in are generated from Makefile.am. I don't want to check in
> generated files, because they will be changed dramatically even you only
> introduce one more file. I cannot find a way to let github generate my
> tarball automatically. Currently, i check the tarball in the git repository
> directly.
> 
> Please let me if you know what is the standard way to generate this
> tarball.

Hello,

GitHub provides a way to distribute release tarballs corresponding to a given
tag:

    https://github.com/blog/1547-release-your-software

You are right that the Git repository should not contain generated files such
as Makefile.in etc.  Similarly, the release tarball should not be committed in
the repository itself.  I recommend to delete idba-1.1.2.tar.gz from it.  This
file will still make the repository heavier as it will stay in the history, but
since it is only 418 kb, maybe the simplest is to ignore that problem.  The
alternative would be to take the opportunity that your repository is very young
to re-do it from scratch.  But anybody who already cloned it would also have to
re-start from a fresh clone.

By the way, since users may prefer to get idba by cloning the repository rather
than downloading a release tarball, it would be nice if you added brief
instructions in the README on how to build it from the clone.  Is it enough
to run “aclocal && automake --add-missing && autoconf” ?

Have a nice week-end,

-- 
Charles Plessy
Debian Med packaging team,
http://www.debian.org/devel/debian-med
Tsurumi, Kanagawa, Japan