Date: Sat, 3 Oct 2015 09:55:31 +0200 From: Baptiste Daroussin <bapt@FreeBSD.org> To: Kimmo Paasiala <kpaasial@gmail.com> Cc: Matthew Seaman <matthew@freebsd.org>, freebsd-pkg@freebsd.org Subject: Re: Provided shared libraries not registering. Message-ID: <20151003075531.GA52626@ivaldir.etoilebsd.net> In-Reply-To: <CA%2B7WWSchc5ZMkWHy16-mkc6qpy4N4weZN=BAxKqmP2TVu-2JMg@mail.gmail.com> References: <CA%2B7WWSdVJCgQzEDxo_dxupkNSwar7yV0cXj5XMNQXpT99DZYLw@mail.gmail.com> <560E3176.2070808@FreeBSD.org> <CA%2B7WWSchc5ZMkWHy16-mkc6qpy4N4weZN=BAxKqmP2TVu-2JMg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--17pEHd4RhPHOinZp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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@freebsd.org> wro= te: > > 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 > > >=20 > 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: >=20 > @shlib lib/libgdal.so.%%PORTVERSION%% >=20 > -Kimmo The right thing would be to fix this library and others, not working around their issues. Best regards, Bapt --17pEHd4RhPHOinZp Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlYPifMACgkQ8kTtMUmk6ExODwCbBe47XZiJ2WVSxzMlqhoPfhYj 2YoAoLss0atYRWNosdNbd7GHLtSOyPTD =v2pN -----END PGP SIGNATURE----- --17pEHd4RhPHOinZp--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20151003075531.GA52626>