Install of pkg fuse-ntfs fails because of undefined symbol in pkg!?!
franco at lastsummer.de
Thu Feb 9 17:00:54 UTC 2017
> On 9 Feb 2017, at 5:53 PM, Steve Wills <swills at FreeBSD.org> wrote:
> What would enforcement look like? Something like "Sorry, you can't pkg
> update because this system isn't supported any more."? But how would
> that be possible without also breaking things for those who build/ship
> their own OS and packages?
Let me try another way:
Since pkg has feature macros for building correctly on different
FreeBSD versions, namely 10.0, 10.1, 10.2 and 10.3, the way to
provide binaries without missing symbols is to build pkg with a
fixed set of feature macros for 10.0.
I've done this for projects to retain upgrade paths. It's not
hard. It doesn't violate a policy or promise FreeBSD makes, does
More information about the freebsd-ports