Wouldn't just including pkgsrc and pkgin with our distro be the best idea? We'd get free access to 12000 ports and we could just build the ports using something like dpb on OpenBSD or poudriere on FreeBSD. I'm not sure what the NetBSD one is for pkgsrc, but I'm sure they have something similar we could use to build all the ports, put them on a file server, and point pkgin there by default.

Remember Greenspun's 10th rule: "Any sufficiently complicated C or Fortran program contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of Common Lisp." and just replace "C or Fortran program" with OS and "Common Lisp" with ports. I think we'd just end up creating a shitty, buggy version of pkgsrc (in any case something worse than the very good pkgsrc) anyway if we tried to roll our own.

I don't know of any Linux distros which have pkgsrc and pkgin as default, so that would make us unique, unless there are distros I'm forgetting. So I think we should:

• Fork pkgsrc
  
• Go through all the popular ports and make sure it all works on Linux
  
• Patch anything that doesn't work (probably won't be that much stuff)
  
• Regularly merge changes from the real pkgsrc tree
  

Considering that most of the programs in pkgsrc already work on Linux, it'd be almost zero effort.