Out of interest, if someone has site-specific software they need to package, but is of no interest to the wider world, how easy is it to host their own repository with that software? (is it like apt where it offers the user a union of an arbitrary number of software repositories?)
Would it be vastly easier in that case to revert to being source based, or is it relatively easy to build binaries and shove them into a repo?
You'll just need to tweak paths from /opt/local (SmartOS) to /usr/pkg (OSX).
The one caveat is that multiple repository support in pkgin is not great right now. It should be ok as long as your site-specific packages are separate from the rest, and have unique names etc. This is something we hope will be fixed during this year's GSOC.
Out of interest, if someone has site-specific software they need to package, but is of no interest to the wider world, how easy is it to host their own repository with that software? (is it like apt where it offers the user a union of an arbitrary number of software repositories?) Would it be vastly easier in that case to revert to being source based, or is it relatively easy to build binaries and shove them into a repo?