On Tue, Sep 07, 2004 at 01:17:41AM +0200, Jesus M. Gonzalez-Barahona wrote: > Sorry if this has been dealt with before (and being such common, > probably it has been). Well, to the topic: there is a lot of software > our there built to use the automake and friends tools. However, upstream > ususually provides a ready to run ./configure script. I've always used > it as the starting point for building the package in the debian/rules > file, but now I wonder why I'm not running all the automake etc. > toolchain before. I know that in most circumstances it would make no > difference, and in any case would add new Build-Depends. > But maybe that > would help to maintain the packages in the long run, specially if I have > to tinker a bit with Makefiles and the like (as is the case with one > package I'm building these days), and probably cannot harm. Quite the opposite. In the long run it causes nothing but harm. Automake and autoconf explicitly do not support this usage, and *will* break. Future versions are *not* source-level compatible with whatever you have at the moment. Running them during the package build process ensures that at some point in the future, your package will become immediately buggy, because it has ceased to build. -- .''`. ** Debian GNU/Linux ** | Andrew Suffield : :' : http://www.debian.org/ | `. `' | `- -><- |
Attachment:
signature.asc
Description: Digital signature