I think that a new category in the portage called "portage-extentions" can be used to hold ebuilds, that would add number of additional ebuilds when emerged. I recently wrote about 10 new ebuilds which sets up qmail+vpopmail+smtp+qmtpd+ssl+webadmin+spamassassin packages and configures them. I think that others might want to benefit from such out-of-the-box installation. Of course i could have a ZIP file in my homepage, but noone wil ever find it there. If there would be a single ebuild in the portage, which pull that ZIP into /usr/local/portage it will be easy to upgrade customly built packages. Reproducible: Always Steps to Reproduce: 1. 2. 3.
umm what exactly are you proposing ?
Create a new category portage-extensions. That would be exact place for my e-builds (they are attached to bug), which build multidomain qmail server(from original description). Then someone might want to create there ebuild to reproduce http://www.gentoo.org/doc/en/virt-mail-howto.xml (Virtual mailgosting with postfix). Courier have a lot of components which could be put alltogether in the extention pack. Games or emacs or sys-cluster could be moved outside of portage into extention packs, since not much use them but they produce much noice during rsync.
Created attachment 7860 [details] ebuilds to create ready-to-use qmail multidomain solution.
Looks like you're suggesting PORTAGE_OVERLAY... If you have a good explanation that doesn't end up being PORTAGE_OVERLAY, reopen.
