seening all the current portage problems and feature requests, I decided to start hacking into portage BUT! how surprised I was when I found out that even an hour of studing the code isn't enough... :-( The code lacks comments so it's VERY hard for everyone outside the current portage-dev-group to understand the basic principles...
I think that if you created some kind of documentation or added the description to every function used and some explanations whenever necessary, the portage development will speed up a lot...
Anyone interested in this?
Radek, don't spose you're up for taking a stab at this?
As a note, I am also trying to figure out portage. Honestly, it's horribly commented, but IMHO it's not that bad. Python is pretty good at letting the code document itself. As far as the whole portage-layout deal, yeah there isn't any documentation for it. From what I've heard, there won't be because most of the internals are being designed and rewritten for the new portage hotness. The newer portage should have documentation.
*notes that he isn't a portage dev and his words are only what he heard from the gnomes on IRC*
Jstubbs says he was taking a stab at ripping out emerge code and commenting it in HEAD.
Marking this later. the code needs better inline commentary- new code/modules are properly documented, the existing stuff (portage.py) is getting there slowly, too.
Emerge is another matter. Anyone who is interested/want this, comment on the portage-dev ml if you're willing to help.
Help would be appreciated.
Not much to have a bug about this.