ok, this part may look obvious for ebuild devs, but personnally I'm just staff for now, so when I wanted to mess out with some ebuilds, I didn't know where to start. This first section would detail all you need to know to start hacking on ebuilds with a decent configuration. At least -Checking out from cvs.g.o -Setting make.conf (PORTDIR_OVERLAY, PORTAGE_ECLASS_WARNING_ENABLE) I can try to write a first draft for this two points, but I'm lacking portage knowledge (solar told me about CLEAN_DELAY, EPAUSE_IGNORE, EBEEP_IGNORE in make.conf, I'm sure there's other useful tips for an ebuild dev that could fit in this section.) Reproducible: Always
Not sure if we really need this... in general I tend to point people to read devmanual :|
As one of the few docs guys, I'm going to say that we're now going to fix this bug. We now have two articles available on the wiki providing 'how to get started' details for our community and our developers. Instructions are also provided concerning pull requests, the proper commit format, etc. See here: https://wiki.gentoo.org/wiki/Gentoo_Github And here: https://wiki.gentoo.org/wiki/Gentoo_git_workflow For ebulid knowledge we have the Devmanual found here: https://devmanual.gentoo.org/ And the Freenode IRC chatroom found at #gentoo-dev-help