Hi,
I would suggest for libpkg/utils.c to extend the warning text (e.g. with a worst-case scenario hint).
Example
Newer FreeBSD version for package foo:
This package was built for a newer ABI than the one currently running.
Installing/using it may cause shared libraries to be unresolvable.
advice: update your kernel
- package: 1501501
- running kernel: 1500507
To ignore this error set IGNORE_OSVERSION=yes
is_valid_os_version() warns when a package's FreeBSD_version is newer than the running system's ABI version, but the message currently only states the version numbers involved
For users unfamiliar with FreeBSD's ABI versioning scheme, this doesn't convey the actual risk of proceeding (or of having already installed such a package). In practice, a mismatch like this can mean that shared libraries under /usr/local/lib are no longer ABI-compatible, causing binaries that depend on them to fail to run — up to the point where large parts of /usr/local stop working.
Hi,
I would suggest for libpkg/utils.c to extend the warning text (e.g. with a worst-case scenario hint).
Example
is_valid_os_version() warns when a package's FreeBSD_version is newer than the running system's ABI version, but the message currently only states the version numbers involved
For users unfamiliar with FreeBSD's ABI versioning scheme, this doesn't convey the actual risk of proceeding (or of having already installed such a package). In practice, a mismatch like this can mean that shared libraries under /usr/local/lib are no longer ABI-compatible, causing binaries that depend on them to fail to run — up to the point where large parts of /usr/local stop working.