I think in the section (or earlier in the intro) 2.ebuild script should be added a section that explain that before writing any ebuild you must check on bugs.gentoo.org if that there is not already one, not yet merged in the portage tree. It may be obvious but was not to me : i ended up writing an ebuild just to see 2 month later there was already one on bugs.gentoo.org not yet included into the main portage tree (because of 1.4 ebuild freeze). I know at least another guy to which it happened. Here's what the section I would add: Before writing any ebuild Check on bugs.gentoo.org that there is not already an ebuild corresponding to the ebuild you want to write, but that has not yet been put into the portage tree: Go to http://bugs.gentoo.org Choose query As product select "Gentoo Linux" As component select ebuilds As status select NEW, ASSIGNED, REOPENED and RESOLVED (RESOLVED is important) Submit the query
[UPDATED] Here's what the section I would add: Before writing any ebuild Check on bugs.gentoo.org that there is not already an ebuild corresponding to the ebuild you want to write, but that has not yet been put into the portage tree: Go to http://bugs.gentoo.org Choose query As product select "Gentoo Linux" As component select ebuilds In the search field put the name of the ebuild As status select NEW, ASSIGNED, REOPENED and RESOLVED (RESOLVED is important) Submit the query
seems good to me. ZhEN?
Cool, I will assign it to myself so that when I do the dev update, it will get included. //ZhEN
Fixed in the updated guide. //ZhEN
