Date: Thu, 9 Feb 2017 17:26:00 +0100 From: Kurt Jaeger <pi@opsec.eu> To: Konstantin Belousov <kostikbel@gmail.com> Cc: freebsd-ports <ports@freebsd.org> Subject: Re: Install of pkg fuse-ntfs fails because of undefined symbol in pkg!?! Message-ID: <20170209162600.GP13006@home.opsec.eu> In-Reply-To: <20170209161249.GL2092@kib.kiev.ua> 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> <20170209161249.GL2092@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi! > 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. On the one hand: Maybe we can agree that the pkg binary breaking between different 10.x versions was unfortunate ? I understand that it was not a break of the ABI promises per se, but I can tell you, I was surprised as well, when it bite me 8-} On the other hand: Getting the ports/pkg tree moving with the velocity necessary to cope with the fast-changing world, sometimes things break and we all try to prevent this. Sometimes, mistakes happen... -- pi@opsec.eu +49 171 3101372 3 years to go !
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170209162600.GP13006>