richardtoohey2 sometimes it just isn't worth to add anything further, I mean, the very first thing I explained in this thread is that llvm from ports is (almost?)
never pulled in for the
compiler, so, of course, changing the llvm version in
DEFAULT_VERSION has nothing to do with the compiler used to build ports. And therefore, the "issue" we're talking about here isn't associated to the thread topic either. Still this guy didn't get it but started to complain in an extremely rude way.
And now, we're at the typical "but I don't want to upgrade" whining we've all seen countless times. Well, it's as simple as that, if you don't want to upgrade your ports/packages, FreeBSD isn't for you. While FreeBSD base has some "long term" support for major releases with stable ABI, ports doesn't. Thanks to the stable ABI, old packages will continue to work (and it's your own problem if you're running into security vulnerabilities with that), but there just isn't any sane way to ever guarantee some old ports tree will
build fine with newer base versions.
Yes, this version jump of the base compiler is surprising. As I said, it won't violate the stable ABI, but one could
still discuss whether it would be better to avoid such things. Still it won't solve the general issue. You have to keep your ports tree up to date, you
can opt for a quarterly branch.
