Re: One source, two binary packages
-----BEGIN PGP SIGNED MESSAGE-----
On 9 Apr 1998, Ben Gertzfield wrote:
> For the GIMP packages, it is required; they ship with a libtool
> that is incompatible with Debian policy. I have to run
> automake/aclocal/autoconf every single time the package builds
> to remove all vestiges of the old libtool and replace it with the
> Debian libtool.
I still don't understand why this has to be done in the *build* target.
Suppose a GNU package has a configure script generated by a buggy
autoconf. The Debian maintainer could add a special target in the
debian/rules which calls autoconf and refreshes configure from
configure.in.
Then the package could be created normally, and the new (fixed) configure
script would be reflected in the diffs.
And then, people compiling the *same* source package for m68k, powerpc,
alpha, or whatever do not need to run autoconf again.
I don't know much about libtool, but is it so much different than
generating configure scripts from configure.in?
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: latin1
iQCVAgUBNS0XOiqK7IlOjMLFAQE9yAP9GgM+RvmPp+fDOcJ6wopxbjOLkniHoxkm
DDK2SAt856tvTl8EhpvX7heB0X0Nq+RdCvvW+SVuXI9JVgtgjXGAaZPT3iEOGIJL
EGRspr+8n84yFrMyIdw2eRchfEMJcRlMUbd97CaoBcHE9QdrlKL408/TJHeEZk0o
Ukbi9eIcmho=
=KqiE
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to debian-mentors-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: