This should probably be one of the targets
I did not consider this too much yet, since I definitely want to wait for Kolab-2.1 to come out. On the other hand the release was expected around december last year. So maybe it's time to start thinking about the format in which the overlay could be migrated to the main portage tree.
One option would be to start a new category net-kolab and stuff all the modified ebuilds in there. This would also have the advantage that it becomes clear that kolab is a seperate thing and does a little bit more to your system than the standard ebuild.
On the other hand it would be possible to ask the maintainers of packages like cyrus-imapd and postfix whether they would accept the additional kolab use flags. I'll probably have to open up some bugs for this.
But I'd also welcome any feedback on how this could be done. Or is the overlay the best solution? I actually wouldn't mind if it would continue to live as an overlay. Just would have to allow to have stable and development ebuilds in there.
