Proxied Maintainer FAQ

Proxied maintainers and Gentoo developers are invited to work on this page and collect FAQ and common mistakes here.

When an ebuild needs a revbump (-r1)
Refer to the devmanual.

Keywording after EAPI bump
An EAPI bump requires usually that all keywords are set to `~` (unstable). This can be done with:

From the package.

However there are some special cases where a stabilization can remain, if the developer can be 100% sure, that the EAPI change does not change anything. But this is not the case for usual packages.

Sorting of KEYWORDS
We usually sort the KEYWORDS values as ekeyword does. This makes comparison between packages easier. Simply run ekeyword on the ebuild to let it sort.

Use the latest EAPI for a pull request
We always try to use the latest EAPI if possible. If a required eclass is not yet compatible with the latest EAPI this can not be fulfilled directly.

"Copy/paste" style of contributions
If you commit new version bump and base your new ebuild on an old ebuild that uses old EAPI and has multiple modern QA issues, you are asked to update your new ebuild contribution to match today's Gentoo standards. However if you fix a bug on a current ebuild that requires a revbump and therefore a new ebuild copy, we will use common sense and accept the contribution to current ebuild revision.

Unfortunately ::gentoo tree is full of outdated ebuilds by modern standards. You can read the devmanual and QA Policy Guide, in addition to EAPI 6 & 7 guides if unsure about state of the current ebuild you're working on.

Breaking tests in parallel building mode
Tests after an ebuild has successfully finished the compile phase run in the same mode (environment). Individual (source-) files can be translated and compiled concurrently and independently from each other. However test-commands can fail when run in parallel!

Parallelism for the make utility is handled via the -j or --jobs Option to make i.e.:.

In those cases the tests and test-commands should be run with the --jobs option explicitly set to 1 i.e.:.

Alternatively:

Using the cmake-util.eclass allows for a direct setting of the --jobs Option :