> "--libdir=..." is used for different way in more than a little
> packages, then SET_LIBDIR=yes will break such packages.
That would be bad, indeed.
> So I want to change as following, same as infodir and mandir:
>
> framework changes:
> * CONFIGURE_HAS_LIBDIR (new)
> "yes" or "no": configure has --libdir option or not
> (will be "yes" by default)
> * GNU_CONFIGURE_LIBDIR (new)
> full path to libdir for the package
> ${GNU_CONFIGURE_PREFIX}/lib by default
> * GNU_CONFIGURE_LIBSUBDIR (exist)
> package specific sub directory of libdir
> ${GNU_CONFIGURE_LIBDIR} will be
> ${GNU_CONFIGURE_PREFIX}/lib/${GNU_CONFIGURE_LIBSUBDIR}
>
> packages changes:
> * change "CONFIGURE_ARGS+=--libdir=${PREFIX}/lib/foo" to
> "GNU_CONFIGURE_LIBSUBDIR=foo"
> * change "CONFIGURE_ARGS+=--libdir=${PREFIX}/bar" to
> "GNU_CONFIGURE_LIBDIR=${PREFIX}/bar"
> * add "CONFIGURE_HAS_LIBDIR=no" if no --libdir support
> * drop "SET_LIBDIR=yes"
>
If I understand you correctly, with these changes applied the behavior
changes like when I do explicity not want LIBDIR, I need to set
CONFIGURE_HAS_LIBDIR=NO
otherwise support is automatically granted.
What's the exact difference between GNU_CONFIGURE_LIBDIR and
GNU_CONFIGURE_LIBSUBDIR in this new setup? It seems a little redundant
to me, but I may be missing something here.
- Volkmar
P.S. the changes will need to be propagated to pkgsrc-wip, too...
--
http://www.dimensionv.de/
http://tech.nifelheim.info/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
OpenPGP
Fingerprint: E03D 33DB B409 2E99 C2DA 7D64 145F 0A76 D252 7078
Key: http://www.dimensionv.de/pgp (+ all public key-servers)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Attachment:
pgpSIrvQkmYET.pgp
Description: PGP signature