"Regarding rolling back/forward, the ports system allows you to create binary packages from your build. So, if you're in a production environment, the old versi

"Regarding rolling back/forward, the ports system allows you to create binary packages from your build. So, if you're in a production environment, the old version of the package still is there, ready to be reinstalled with all your compile flags intact." This doesn't sound equivalent to: yum install httpd-<specific-older-version> To me. What does that look like, exactly? What are the steps to roll back to a prior version? "Verification is also something that ports does. Because ports work with the pkg system, installing a port installs it in a package, with hashes and everything. Auditing's a no brainer there." I now see this is true; apologies for misleading statements above. The pkg_check command seems to do what is necessary here. That's great! "Furthermore, the ports system allows you to build everything within jails dedicated to port building, so every time you update, you get fresh packages with no legacy dependencies." Again, what does that look like? What are the commands? How long does it take? "So, again, you get everything apt and rpm can do, plus you get a level of flexibility that they can't match." I think we may both be speaking from positions of ignorance. I'm gonna go install an OpenBSD VM and fix my ignorance.