tracking upstream's git repo and autotools

[Pierre Habouzit]

On Sat, Feb 16, 2008 at 11:33:26PM +0000, Russ Allbery wrote:
> Jan Luebbe <jluebbe at lasnet.de> writes:
> 
> > I'm trying to come up with a good way to package directly from
> > upstream's git repo, which doesn't contain the files autogenerated by
> > autogen.sh.
> 
> I would just Build-Depend on autoconf, automake, and the like and run them
> during the build.

  It takes a lot of time, and prevents builds repeatability, in the
sense that when autotools have backward compatibility issues, it breaks,
not to mention that you need all the *.m4 files around to generate the
configure properly.

  FWIW, the autoconfiguration of the upstream source is just another
patch to apply at build time. Even with properly "autoconfigured"
upstream, you often want to autoreconf and or relibtoolize (to support
kfreebsd and friends or avoid libtool amd64 rpath issues).

-- 
·O·  Pierre Habouzit
··O                                                madcoder at debian.org
OOO                                                http://www.madism.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/vcs-pkg-discuss/attachments/20080217/6a4b55dd/attachment.pgp