Re: libtool varying versions
-----BEGIN PGP SIGNED MESSAGE-----
On Tue, 17 Mar 1998, Marcelo E. Magallon wrote:
> On 16 Mar 1998, Ben Gertzfield wrote:
> > Do I remove the newer libtool from the upstream source and replace
> > it with the current libtool in the Debian distribution?
> add "libtoolize --force --copy" to debian/rules. This would make
> your package source-depend on libtool. And automake maybe.
> Definitely autoconf. In the process Makefile.in -> Makefile the
> m4 macros are expanded, and ./configure should be regenerated
> just to make sure the libtool m4 macros are not different from
> those used upstream.
Well, it was agreed (more or less) that no Debian package should depend on
automake, autoconf, or libtool (it is not needed), because no GNU
package depends on any of these tools either (if GNU can do it, we can do
it as well).
I would suggest to add a rule "libtoolize" to your debian/rules files
so that it will only have to be called by you *before* creating the
This way, this special rule would not have to be called by people
compiling the package for m68k, powerpc, etc. and there would not be any
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----
To UNSUBSCRIBE, email to firstname.lastname@example.org
with a subject of "unsubscribe". Trouble? Contact email@example.com