Re: [gentoo-dev] A wishlist

[Dan Armak <danarmak@gentoo.org>]

Some followups and suggestions:

For the documented portage API:
I don't mind it being in python, although c/c++ would be nice sometime down 
the road. This is a must for all the stuff karltk calls Gentool.Configure.
At least, I wish for a short summary of the portage.py api. I tried reading 
it through; there are no comments at all.

For the ebuild review team:
They could have several separate Gentoo installs. Maybe in chroots.
One would be empty (emerge system only), good for checking depends. Ebuilds 
are unmerged once they are confirmed to be working.
Another would have all existing ebuilds installed, good for checking 
conflicts. It would also have all revs installed, good for checking upgrades 
and different dep version scenarios.
We could have [at least] two devs on the team, one for each of these configs, 
running emerges in the background whenever they aren't using the cpu. Say on 
non-main machines.
Of course, there'll probably also be a more standard testing machine.

For the ebuild layout (Martin's wish):
IMHO one of the best things here, beyond guides and docs, is eclasses. They 
ensure maximum standardization, and a lot of other fun things too.

-- 

Dan Armak
Gentoo Linux Developer, Desktop Team
Matan, Israel