Every ebuild must specify a KEYWORDS variable. [1] But this is not the case as said in https://bugs.gentoo.org/show_bug.cgi?id=545444 [1] https://devmanual.gentoo.org/keywording/index.html Reproducible: Always
Can you provide a patch?
This is not true sorry repoman full on an ebuild without KEYWORDS will simply report the following warning (eg on a modified redis ebuild): RepoMan scours the neighborhood... KEYWORDS.missing 1 dev-db/redis/redis-3.0.0.ebuild So I don't think we need to fix the devmanual.
Since this is a warning you can still commit the ebuild which will assume KEYWORDS="" but devmanual is about documenting good practices etc so committing ebuilds with repoman warnings is not something we should encourage in documentation.
What repoman reports depends on the situation. For a regular ebuild without KEYWORDS it will indeed report this: (In reply to Markos Chandras from comment #2) > KEYWORDS.missing 1 > dev-db/redis/redis-3.0.0.ebuild (Note that it doesn't distinguish between the KEYWORDS="" and unset KEYWORDS cases.) It is different for a live ebuild, though. Here repoman will be happy if the ebuild _doesn't_ assign a KEYWORDS variable. However, after adding KEYWORDS="~amd64" to the live ebuild, I'll get this: RepoMan scours the neighborhood... LIVEVCS.unmasked 1 app-doc/pms/pms-9999.ebuild
Hmm i see. Ok i guess we can re-word it a bit to mention that KEYWORDS is necessary for non-live ebuilds
Created attachment 403736 [details, diff] Proposed patch
commit 1362d6608c323241ad1a4d0313046e99407ef352 Author: Ulrich Müller <ulm@gentoo.org> Date: Thu May 21 18:37:11 2015 +0200 Live ebuilds need not specify KEYWORDS. Bug 545488.
