Date: Tue, 8 Mar 2016 13:51:45 +0000 From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-pkgbase@freebsd.org Subject: Re: [CFT] packaging the base system with pkg(8) Message-ID: <56DED8F1.8030606@FreeBSD.org> In-Reply-To: <20160308131847.GP1531@FreeBSD.org> References: <20160302235429.GD75641@FreeBSD.org> <20160308124016.GA70809@zxy.spb.ru> <20160308131847.GP1531@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --BlmEj2v2v1drQ009eeqLuDRPUTmIcc0Vh Content-Type: multipart/mixed; boundary="2L0iSuUOcxgiuJlbPC1rhAwgQ3wq4u52e" From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-pkgbase@freebsd.org Message-ID: <56DED8F1.8030606@FreeBSD.org> Subject: Re: [CFT] packaging the base system with pkg(8) References: <20160302235429.GD75641@FreeBSD.org> <20160308124016.GA70809@zxy.spb.ru> <20160308131847.GP1531@FreeBSD.org> In-Reply-To: <20160308131847.GP1531@FreeBSD.org> --2L0iSuUOcxgiuJlbPC1rhAwgQ3wq4u52e Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 08/03/2016 13:18, Glen Barber wrote: > Regarding the .so files, I am not clear on the original intent behind > separating the actual shared library from the installed symbolic link t= o > the real shared library, but in my investigation into this, only the > symlinks are provided by the '-development' package. Once compiled, a program will dynamically load a specific ABI version at run time -- it needs to refer to a shared library filename including some version numbers. However at compile time a program may be able to link against various different ABI versions of a shlib, so long as the API is still the same (and established APIs tend to change much more slowly than ABIs). So end-users need the shared library name with all the version numbers, but developers (generally) want the sym-link that points at the locally preferred version of the shared library. There's also considerations to do with being able to install a number of different ABI versions of the same shared library simultaneously. There's nothing intrinsic to shared library versioning to prevent this, but having the sym-link in every shared library package would automatically make the different ABI-version packages conflict with each other. Cheers, Matthew --2L0iSuUOcxgiuJlbPC1rhAwgQ3wq4u52e-- --BlmEj2v2v1drQ009eeqLuDRPUTmIcc0Vh Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQJ8BAEBCgBmBQJW3tj5XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxOUYxNTRFQ0JGMTEyRTUwNTQ0RTNGMzAw MDUxM0YxMEUwQTlFNEU3AAoJEABRPxDgqeTnTeoQAJe3plLCuY0+4go6a7+2OKWa vXu8UE0ZnT9Gk3OQ/eqZw1BJ5selWesK1yUcBUxTGGM5wJcOgoOtbHeRX0z+9xjy vyAK2y9fXF+saOPCwVKk4NdbGceH1cAdRSiHjAyzR3n/ZuUund3hArS+SRIaOeoO 1HfKvvK+wfqHx7z6nW4X0Lt2MLkSL9LC6nspwU8GrZAlMPVnLIcZ0YEnSx7YBuqK l6hdtwndXUextGxV+nBmWH8qtX32h4HYn11zJvCAxXPR8nQRTAgezRdkPP6pVN0i hclIBOVALNXNc/7F+KpBqclYkm9WirV+UqGNz+IzG7K5MOzQV7O6jxy1ElnY4owX yoV7eGkKDUXe521rUSQLAZUfgbQC0U/+GaTjlnYRBbsAyxRsttI/Sv+wTQT+TOmM h60Ztw0iR5IswFaaMNURBcOgL8At3VPNqT6QVzjS5O+AhsyFR+NdT47usXUcK2lo UV0R5r9VsVYAMfkVm/vGBTWK52V/pMpwKNcayGTNEZsbkfFOlHrEgSvu9+mnMZbf DF4jeT6qjw9gE4i2UDEtFXMmBFc8Yma3HuBV+Cn23gDGie2pGRfWxJXepbxuk3MF XWtC6KHYgHQoIByWWlwv5z0ERi1aqyelz2JLj10iKhhZ20QivUVVoV13jWpyTwig yX9RDaIR6ynUBuuBxxwM =TSir -----END PGP SIGNATURE----- --BlmEj2v2v1drQ009eeqLuDRPUTmIcc0Vh--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56DED8F1.8030606>