Provided shared libraries not registering.

[Baptiste Daroussin]

On Fri, Oct 02, 2015 at 11:55:42PM +0300, Kimmo Paasiala wrote:
> On Fri, Oct 2, 2015 at 10:25 AM, Matthew Seaman <matthew at freebsd.org> wrote:
> > On 02/10/2015 08:27, Kimmo Paasiala wrote:
> >> This came up on graphics/gdal but there could be others. It looks like
> >> pkg doesn't register provided shared libraries if the libraries lack
> >> an SONAME in their dynamic section. Was this changed on pkg 1.6 or has
> >> it always been like that? What it does now is that 'pkg check -d' will
> >> complain about missing shared libraries that are present and
> >> applications using those libraries work fine.
> >
> > Yes, that was a deliberate choice.  Not all shared libraries are created
> > for sharing -- and some times it's hard to tell whether something is
> > meant to be a loadable module rather than a shared library.  In theory
> > these are quite different binary formats, but it seems many developers
> > don't appreciate the subtleties, and mix up the two.  It's a heuristic
> > that does as well as we could manage, but that doesn't mean there isn't
> > room for improvement.
> >
> > The test on SONAME has been in the code for quite some time, certainly
> > since before pkg-1.5.0
> >
> >         Cheers,
> >
> >         Matthew
> >
> 
> How hard it would be to implement a new keyword, let's say @shlib that
> you could use to explicitly declare a file a provided shared library?
> For example:
> 
> @shlib lib/libgdal.so.%%PORTVERSION%%
> 
> -Kimmo

The right thing would be to fix this library and others, not working around
their issues.

Best regards,
Bapt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-pkg/attachments/20151003/0deaafd1/attachment.bin>