3 ms·
I enjoy OpenBSD and I would use it production if it weren't so hard to build and distribute packages that target it. On Linux, installing packages can transfor
by elevation 5y ago
I enjoy OpenBSD and I would use it production if it weren't so hard to build and distribute packages that target it.
On Linux, installing packages can transform a system from just the base OS into a functioning part of my infrastructure. I can pull FOSS software from the repos, but if I need more control over security patches I can easily build and package my own server, database, scripting languages, and I can sign these packages and host them in my own custom repo. I can also package things that aren't programs, such as CA public keys, artwork, even backup/restore points. I can package closed source software that isn't suitable for hosting in the public repos.
On OpenBSD, the "ports" use case appears to be only for FLOSS software that's built and publicly hosted by the ports team. If I want to package something into the equivalent of a deb/rpm without submitting it to be hosted on the ports server, or use `pkg_add' to install a package I made myself, search results make it seem like I'm about the first person to ever have tried it. Is there nobody building or hosting their own org-specific ports?