diff options
authorGokturk Yuksek <>2015-12-30 07:10:38 -0500
committerJustin Lecher <>2016-01-06 17:56:38 +0100
commitbd38eccad73e30f6b9297e477e7e359ed4c7c705 (patch)
parentUpdate version (diff)
ebuild-quiz: revise docs to replace instances of handbook #546542
Gentoo Developer Handbook does not exist anymore. Replace any instances of "docs: handbook" with the appropriate equivalent source which is either "devmanual" or "wiki". Ebuild Question 15 speficies handbook as the source. Upon examining devmanual and contacting developers on #gentoo-dev-help, it became clear that this is an open ended question and none of the docs have an answer for it. In the light of this, the question is modified to specify no docs. The actual links of the sources aren't included in the quiz text. They are included here instead: *** Organizational structure questions Question 9 sources: - *** Ebuild technical/policy questions Question 2 sources: - - Question 3a sources: - - Question 3b sources: - - - Question 4 sources: - Question 10b sources: - Question 13 sources: - Question 15 sources: - No docs available. Question 16 sources: - Question 19 sources: - Gentoo-Bug-URL: Signed-off-by: Gokturk Yuksek <> Signed-off-by: Justin Lecher <>
1 files changed, 11 insertions, 11 deletions
diff --git a/recruiters/quizzes/ebuild-quiz.txt b/recruiters/quizzes/ebuild-quiz.txt
index 0768145..8d6dd78 100644
--- a/recruiters/quizzes/ebuild-quiz.txt
+++ b/recruiters/quizzes/ebuild-quiz.txt
@@ -1,4 +1,4 @@
-# Copyright 1999-2015 Gentoo Foundation
+# Copyright 1999-2016 Gentoo Foundation
# This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
Ebuild development quiz
@@ -47,7 +47,7 @@ docs: devmanual
9. What is the devaway system?
-docs: handbook
+docs: wiki
*** Ebuild technical/policy questions
@@ -61,23 +61,23 @@ docs: devmanual
2. A user submits a "live" VCS (git, svn ...) ebuild. What would be a preferable
alternative to such an ebuild?
-docs: handbook
+docs: devmanual
3. (a) What is repoman? How would you check for QA problems with
-docs: handbook
+docs: devmanual, wiki
(b) A user submits a brand-new ebuild for a new package. What are the
proper steps (including repoman commands) to take to add
this ebuild to the tree?
-docs: handbook
+docs: devmanual, wiki
4. A user submits an ebuild that has numerous technical problems and
violates policy. How would you handle that situation?
-docs: handbook
+docs: devmanual
5. You have a set of new ebuilds that could potentially benefit
from a global USE flag. What steps should be taken before
@@ -118,7 +118,7 @@ docs: devmanual
KEYWORDS. It was previously hard-masked in package.mask.
What should be done prior to doing so?
-docs: handbook
+docs: devmanual
(c) You wish to have an ebuild marked "stable." It is a popular
application, but no other ebuilds depend on it.
@@ -139,7 +139,7 @@ docs: devmanual
ChangeLogs and metadata.xml and it appears to be maintained by
someone else. How should you proceed?
+docs: devmanual
14. You find a situation in which an eclass may be useful. What should
you do before implementing such an eclass?
@@ -149,12 +149,12 @@ docs: devmanual
15. How can you verify an ebuild has correct run time dependencies
(RDEPEND) for all installed binaries?
-docs: handbook
16. How do you deal with a situation in which an ebuild wishes to
install a file already installed by another package?
-docs: handbook
+docs: devmanual
17. Most configure scripts attempt to automatically determine
settings based on the host system. When should the ebuild
@@ -168,7 +168,7 @@ docs: devmanual, PMS
19. What is the procedure for removing packages from the tree?
-docs: handbook
+docs: devmanual
20. How do keywording policies for less often used arches like ia64 or
mips differ from the more common ones like amd64?