On Tue, 14 Jul 1998, Alistair Crooks wrote:

: (1) on ELF platforms, the ${PLIST} file will be scanned for a
: lib/libfoo.so.x symbolic link. If none is there, it will be created and
: added to the ${PLIST}, just after libfoo.so.x.y. The same happens for
: libfoo.so. Whilst this does not cure all the problems with shared libs on
: ELF platforms, it should go a long way to ironing out some of the problems
: that have arisen. 

I was actually going to ask about this w.r.t. using libtool in pkgs.  Looks
like I don't have to ask, now.  :>

: (2) on a.out platforms, the @exec ${LDCONFIG} and @unexec ${LDCONFIG}
: lines will automatically be added to the ${PLIST} file, if they're not
: already there, and an ${LDCONFIG} command will also be issued.

Does this still do the || true clause, for non-shlib systems?  (The current
handling may need to be modified one more time, if libtool is adopted, to
compensate for NOPIC systems.)

I'll be committing a pkg (w3c libwww) later today that makes use of an
installed libtool to demonstrate one way it can be used (...and will make
use of your new auto-shlib handling). 

-- 
-- Todd Vierling (Personal tv@pobox.com; Bus. todd_vierling@xn.xerox.com)