Subject: Re: take2; using pkglibtool
To: Kazuki Sakamoto <sakamoto@cec.co.jp>
From: Hubert Feyrer <feyrer@rfhs8012.fh-regensburg.de>
List: tech-pkg
Date: 12/07/1999 08:10:39
On Tue, 7 Dec 1999, Kazuki Sakamoto wrote:
> > > LTCONFIG_OVERRIDE=${WRKSRC}/ltconfig
> > > LIBTOOL_OVERRIDE=${WRKSRC}/libtool
> >
> > Um, even after looking at the patch, I'm not sure I understand the
> > difference between LTCONFIG_OVERRIDE[*] and LIBTOOL_OVERRIDE. They both
> > seem to name the path of the libtool?
>
> "ltconfig" is script to make "libtool" script.
> "ltconfig" is executed by GNU's "configure" script at "do-configure" target.
>
> if USE_LIBTOOL and LTCONFIG_OVERRIDE defined, specified "ltconfig"
> is overrided to symlink pkglibtool to "libtool" instead of making
> "libtool" before executing "configure".
>
> if USE_LIBTOOL and LIBTOOL_OVERRIDE defined, specified "libtool" is
> removed, and symlinked from pkglibtool after executing "configure"
> (and "ltconfig").
>
> In most cases, LTCONFIG_OVERRIDE is useful and LIBTOOL_OVERRIDE is
> not needed. When software has already original "libtool" which we can
> substitute by pkglibtool, LIBTOOL_OVERRIDE is useful.
>
>
> > Please don't forget pkgsrc/Packages.txt... :-)
>
> Please help my poor English :-)
Things are clearer now. The above should do to get an idea. :)
- Hubert
--
NetBSD - Better for your uptime than Viagra