Install of pkg fuse-ntfs fails because of undefined symbol in pkg!?!
franco at lastsummer.de
Thu Feb 9 16:14:14 UTC 2017
> On 9 Feb 2017, at 5:12 PM, Konstantin Belousov <kostikbel at gmail.com> wrote:
> 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
You're contradicting yourself here. Either it's compatible or it isn't?
More information about the freebsd-ports