That said: I need more stuff than the ports tree contains (I .. checked NetBSD and FreeBSD, plus a couple of Linux distributions. I admit that I haven't checked all my packages against OpenBSD's ports tree, but I assume I'm correct). Plus, I do need the occasional update without waiting 6 month. How would I do that?
For comparison: On FreeBSD I use portshaker to create a ports tree that is a mixture of upstream (FreeBSD) and other sources (a git repository, in my case). If FreeBSD doesn't bump a package and PRs take a whiiiiile, I bump that thing in my overlay.
poudriere allows me to build (in bulk) all my relevant packages in jails, is clever enough to rebuild just the stuff that changed (or where I changed the config) and spits out a directory structure that represents a pkgng repository with (optional) signed binary packages.
pkgng is pointed to my repository (actually it supports multiple sources, apt like. Can PKG_PATH do that?), which contains now builds from upstream ports and my overlay.
How would I (hoping that you have a couple of minutes and can prove me wrong once more)
- build binary packages for ports that either don't exist upstream (stuff I ported) or are outdated upstream?
- distribute those in a decent way (PKG_PATH swapping..?)
I guess I'm left with the question whether we're talking about the same thing when we're saying 'decent binary packages'? I'm sure you can OpenBSD works well for the intended use - but 'decent' wasn't an objective attribute here, it was more a subjective 'decent for my needs' kind of thing. More details above.
In the end, pkg_* feel like ooold Solaris, or like using Slackware again. That's package management on a different level and feels like a step down from apt/yum/pacman/pkgng. Again: Probably it's just a matter of convenience and my laziness in the end, but so far I feel that's not for me.