I'm writing an ebuild for some package, and I think some installation task in this ebuild is common for many packages, I want to check whether this common function has been provided by some eclass or not, but there are no online eclass reference at all, the ideal place for it will be the "Gentoo Development Documentation": http://www.gentoo.org/doc/en/index.xml?catid=gentoodev In addition, I have searched on the web and found there are some several eclass reference here, but not full list: http://devmanual.gentoo.org/eclass-reference/index.html I have installed app-portage/eclass-manpages, but these manpages didn't help much, there's need for online documentation. thanks.
We don't maintain the devmanual. The devmanual is clearly marked as the property of QA -- qa@gentoo.org, so bugs for it should be addressed to them. Also, the devmanual does have good material on the eclasses, but you should also read the eclasses themselves to see how they work. Also, check the developer handbook at http://www.gentoo.org/proj/en/devrel/handbook Support requests like this really shouldn't be filed in Bugzilla. A better place would be the Gentoo Forums (http://forums.gentoo.org) or the IRC channel: #gentoo-dev-help on irc.freenode.net
Denis, I would like to add eclasses are bash script and are very easy to read. So use source as a reference - that's very easy in this case.
I think we can parse every function and its comments from every eclass scripts, generate a basic eclass reference, and put it under gentoo.org/doc/ .
(In reply to comment #3) > I think we can parse every function and its comments from every eclass scripts, > generate a basic eclass reference, and put it under gentoo.org/doc/ . And this is already done with eclass-manpages. Not all eclasses are have such descriptions but some do and some patches to make eclasses manpages ready are pending. If you wish to help here you just need to convert existing comments in eclass to eclass-manpages format and attach diff to bugzilla (like mren does in bug 210058 and similar). Enjoy.
any sort of manual step is doomed to failure. this is really a dupe of Bug 202656.
