Date: Thu, 9 Feb 2017 18:12:49 +0200 From: Konstantin Belousov <kostikbel@gmail.com> To: Franco Fichtner <franco@lastsummer.de> Cc: Steve Wills <swills@freebsd.org>, scratch65535@att.net, freebsd-ports <ports@freebsd.org> Subject: Re: Install of pkg fuse-ntfs fails because of undefined symbol in pkg!?! Message-ID: <20170209161249.GL2092@kib.kiev.ua> In-Reply-To: <AE0D514C-D235-462D-B31D-66FC619D9F4D@lastsummer.de> References: <dvvl9chf9h22dpjto35d44enid819p9rnc@4ax.com> <h91m9cpbmp6js1km1bson74he5uuui9r6h@4ax.com> <1c6cccac-b151-d13c-c763-b336c4680118@freebsd.org> <ndjm9cl4samqgioi25ro8p2q6liimvr1h4@4ax.com> <35a953e3-918b-fc32-d990-51f7da16c884@FreeBSD.org> <AE0D514C-D235-462D-B31D-66FC619D9F4D@lastsummer.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Feb 09, 2017 at 04:30:20PM +0100, Franco Fichtner wrote: > FreeBSD package management makes an ABI promise in the form of > "FreeBSD:10:amd64", but not even pkg code itself adheres to this, > and thus we have had subtle and yet fatal breakage in 10.2 and 10.3. Stop spreading FUD. There is no ABI breakage on stable/10 branch, nor there is a breakage in the package sets. We only promise backward-compatibility, and this works as advertized. A binary compiled on later system, is not guaranteed to work on the early system even on the same branch. The current package set for stable/10 is built on 10.3 and is only guaranteed to work on 10.3 and later. Trying to make arbitrary combinations of binaries and base systems outside of the scope of the project.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170209161249.GL2092>