Re: Conflicting library names in ksh and libast / eterm

[Luis Falcon <falcon%gnuhealth.org@localhost>]

Hi, Greg
On Tue, Sep 29, 2026 at 12:50:52PM -0400, Greg Troxel wrote:
> Luis Falcon <falcon%gnuhealth.org@localhost> writes:
> 
> > It seems like Korn shell and lbast (eterm dependency) share the same library name, so pkgin refuses to install the package(s).
> >
> > 2026-09-29T14:53:15Z [4/4] installing eterm-0.9.6nb7...
> > pkg_add: libast-0.7nb14: conflicting PLIST with ksh93-1.0.10nb3: lib/libast.so
> 
> I guess that's an upstream bug for not reserving libnames in the Unified
> Libary Name Registry.  But seriously, not sure how to fix this other
> than renaming one of them, or "don't do that".   I suppose you could
> file upstream bugs with both and see if one of them moves.
> 
Is nice to see how many packages today include their libraries inside a
directory with the package name. 

When we look at /usr/pkg/lib, there are libraries on the lib root dir (eg,
libast.so) and others inside their parent dir (eg, zathura/libcb.so).
The former is susceptible to collisions, the latter is quite safe, 
intuitive and highly recommended :)

PS. Yesterday I had a nice talk on IRC about LD_LIBRARY_PATH . Some
NetBSD hackers told me why we should not use the variable and about 
RPATH [1] magic. Very nice and somehow related to this :)

1.- https://www.netbsd.org/docs/elf.html

Best,