Re: the case of untracked base shlibs

On May 12, 2026 9:07:48 PM GMT+03:00, Warner Losh <[email protected]> wrote:
>
>We try super hard for binaries in base to retain compatibility. For ports
>we don't try at all. so mixing ports from different eras produces lots of
>different conflicts. Some specific subsets of ports can be 'cross threaded'
>like that, so long as they are a self-contained set that only links to the
>base.


i literally laughed at cross threading ports

but, what happens when i use libs from some ports of 13 in a kernel of 14 and other ports of 14?

i don't need to. that's just question what would happen as right now i don't see a failure here

when does it fail?

i get that kernel modules will fail. perhaps some other things

the whole idea was to upgrade affecteds first. not postponing it all. but as i see no failures, is there even a need

then, i can't comment if upgrading "consumer" ports first is bad, and then "provider" ports. i haven't had many failures over that

funnily most of software is maintained, fixed, updated, so it's not like it remains there forever

right now there are perl ports and what else on 13 still, rest of it have been upgraded either due shlibs or just regular upgrade

of course upgrade all is for sure

just like rebooting machine is real check if it comes back up or not