-----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 package. 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 source-depends. -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia Charset: latin1 iQCVAgUBNQ6WaSqK7IlOjMLFAQEFeQQAiLbEDV1nwsJpeZY97lcjo2CGIQqilyIQ fY7WiihDYL5VunloLF9uAKurYtSfr16v79C0a8+y0yH1rVBlWQ31KlPsFx8H3J+w 5CvAW//YRBzpHpZyPVZ9otNIAEwxwCsVnkT81O0zkDJx2+sT2ROZhmsI66u3p1H6 WxA7qtAbV9k= =af3z -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
