Date: Sat, 4 Jun 2016 18:20:24 +0100 From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-ports@freebsd.org Subject: Re: old ports/packages Message-ID: <57530DD8.9070605@FreeBSD.org> In-Reply-To: <3ae2f03e-2753-0a75-0123-9f85c05b0eaf@hiwaay.net> References: <03cc4012-026e-c007-09e1-ee45524f1b95@elischer.org> <B32DD056A6281C191CD35AA2@ogg.in.absolight.net> <c528a76d-5b94-01a3-f27e-7d174faf544e@freebsd.org> <1FAFDF989841D03604BB448B@atuin.in.mat.cc> <7b8d22c6-1fed-d517-9f89-693b88dfc358@freebsd.org> <20160504070341.GV740@mail0.byshenk.net> <3dfd6fea-da32-b922-65d1-f64b8e113112@toco-domains.de> <6e340f95-6d10-4991-0cd6-95d336e2f044@gjunka.com> <3e55c7d8-801c-a2b3-e92e-9945e896142b@toco-domains.de> <5809f808-8b16-93ed-5351-828a7d68eb2b@unsane.co.uk> <c71c19de-f712-6116-cdb3-10580054ab23@toco-domains.de> <574ED144.1050603@quip.cz> <9D785F08-AB0B-4324-B1B3-286D90AF9BF7@lastsummer.de> <20160603172313.3b2353b0@raksha.tavi.co.uk> <daf63beb-5450-3055-17f7-b706b343e42d@FreeBSD.org> <de42dfb6-3b51-a02a-a370-7a626b1ac3fa@gjunka.com> <2d6eddea-0de7-6963-c1ca-a734aaa5a75a@FreeBSD.org> <3ae2f03e-2753-0a75-0123-9f85c05b0eaf@hiwaay.net>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --fw90bAwigfvt3xjLBoS3BdTo2cHENrlJ2 Content-Type: multipart/mixed; boundary="8C4FUHfiQJvetMcSqkCacEXrRWpXXIcJ6" From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-ports@freebsd.org Message-ID: <57530DD8.9070605@FreeBSD.org> Subject: Re: old ports/packages References: <03cc4012-026e-c007-09e1-ee45524f1b95@elischer.org> <B32DD056A6281C191CD35AA2@ogg.in.absolight.net> <c528a76d-5b94-01a3-f27e-7d174faf544e@freebsd.org> <1FAFDF989841D03604BB448B@atuin.in.mat.cc> <7b8d22c6-1fed-d517-9f89-693b88dfc358@freebsd.org> <20160504070341.GV740@mail0.byshenk.net> <3dfd6fea-da32-b922-65d1-f64b8e113112@toco-domains.de> <6e340f95-6d10-4991-0cd6-95d336e2f044@gjunka.com> <3e55c7d8-801c-a2b3-e92e-9945e896142b@toco-domains.de> <5809f808-8b16-93ed-5351-828a7d68eb2b@unsane.co.uk> <c71c19de-f712-6116-cdb3-10580054ab23@toco-domains.de> <574ED144.1050603@quip.cz> <9D785F08-AB0B-4324-B1B3-286D90AF9BF7@lastsummer.de> <20160603172313.3b2353b0@raksha.tavi.co.uk> <daf63beb-5450-3055-17f7-b706b343e42d@FreeBSD.org> <de42dfb6-3b51-a02a-a370-7a626b1ac3fa@gjunka.com> <2d6eddea-0de7-6963-c1ca-a734aaa5a75a@FreeBSD.org> <3ae2f03e-2753-0a75-0123-9f85c05b0eaf@hiwaay.net> In-Reply-To: <3ae2f03e-2753-0a75-0123-9f85c05b0eaf@hiwaay.net> --8C4FUHfiQJvetMcSqkCacEXrRWpXXIcJ6 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2016/06/04 16:14, William A. Mahaffey III wrote: > One point of order if I may: It was stated earlier in the thread that > binary compatibility throughout a major release cycle (X.n-R, as 'n' > varies) is a specification. That is not explicitly addressed in the > above URL's, as far as I can see. Is that indeed considered a > specification ? If so, it would seem to satisfy the LTS desire > implicitly. TIA & have a good one. At the moment we have a guarantee of binary compatibility for any software compiled on release X.n to be able to run on any release X.m where m >=3D n. This is not going to change with the new support model. ie. Something compiled for 11.0 will run on any subsequent 11.x release, but something compiled on 11.3 (say) would not necessarily run on 11.2. Now, in fact, that sort of backwards compatibility usually does work, but it isn't guaranteed. Putting in this sort of backwards incompatible change is something that is avoided unless there is some very good reason to introduce it. Also recognize that libc.so in 11.x will support ABI multi-versions -- so you can run anything that needs an earlier ABI version without any special configuration[*]. This does not apply to all of the shlibs provided by the system, so you may get mixed results depending on what your applications link against. This is why the FreeBSD packages are always built on the earliest still supported release from the same major branch. The difference implied by the new support model is that the package building machines would be updated more frequently as they track the earliest still-supported release. Practically speaking, as a pkg user you're unlikely to experience any difficulties even if you aren't up to date with your OS patching, but there may be some rare occasions where you will need to update your OS before you can update your ports. Cheers, Matthew [*] IIRC the available version history goes back to 10.0-RELEASE; you'll definitely need compat libs for anything compiled earlier than that, but you may well be able to run 10.x applications on an 11.x system with no compatibility shims required. --8C4FUHfiQJvetMcSqkCacEXrRWpXXIcJ6-- --fw90bAwigfvt3xjLBoS3BdTo2cHENrlJ2 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 iQJ8BAEBCgBmBQJXUw3dXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxOUYxNTRFQ0JGMTEyRTUwNTQ0RTNGMzAw MDUxM0YxMEUwQTlFNEU3AAoJEABRPxDgqeTnMt4P/Aq+/RzOjTChaWj4iVd1Z43r aacXu12oweWB9SUP+PQi58/uEXw+SByMEJMgn7gX5yPTk6/ukn0D7p5SEPSNRGaq aRMCIQsU9RYKCushIxOtVOieCKfriflZdTRBwPOviCehzXDRLCzExT3a/6n91JZT KVpuf3qJDOk/C6AbG7p37gkA7o+1DlTB8YE78ZZSGt2K76V71mW5+TxI/+4dr3se E6hzYcIKJv3CrwvRhsydQ9TsQ1Tuy2x1FxVXiyP1akvqouK5Un8+GdA+33vGldXa BiGZ+NlYx0OvCoep+LCGUQRWSFy13BnvxYRcaK2Alunj3vWs4yI3Mg6fLzIBjClU WOG6rchQJgRqhRBQyr9JkRD0tK/LmJddxf66nddz6mn+2vo3RqocOOuHQTjWCAfP KZ6SFZuHt85s8GsqT7FWpt0HXMAFnbGVA+Dyzokhd7Ho8HnP5WC7O5OSnNuGMbPJ CX06xj9aVurmkxDer+0pTCcm6XQlcvigie4z9iR6DsdUXkMtdM9KzDwSGRACQSYe 6p98ldn/dvvzY+5pq6Tq6abtGP/9d3JizTkP4C4TX2B/uNy7I7/BhoCoHX1RL+tw xv6jxIq/QY5oIsVvA5rIm2Bkz4W5eqtad8cMrXi+Zyd72nl+uuyAgtX66sI3fouv J5sAP4GKpFPm0VlkUAQc =IJxm -----END PGP SIGNATURE----- --fw90bAwigfvt3xjLBoS3BdTo2cHENrlJ2--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?57530DD8.9070605>