Re: Conflicting library names in ksh and libast / eterm

[Ted Spradley <tsprad%talent-free-studios.com@localhost>]

On Tue, 29 Sep 2026 12:50:52 -0400
Greg Troxel <gdt%lexort.com@localhost> wrote:

> 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.

set$ pkgin avail | grep '^lib' | wc -l 
     703

And that's only the packages whose names start with 'lib', there are
many more libraries that don't. I'm surprised this issue doesn't come
up more often.

-- 
Ted Spradley <tsprad%talent-free-studios.com@localhost>