diff options
| -rw-r--r-- | recruiters/quizzes/ebuild-quiz.txt | 55 |
1 files changed, 29 insertions, 26 deletions
diff --git a/recruiters/quizzes/ebuild-quiz.txt b/recruiters/quizzes/ebuild-quiz.txt index 080d6df..8d3214a 100644 --- a/recruiters/quizzes/ebuild-quiz.txt +++ b/recruiters/quizzes/ebuild-quiz.txt @@ -1,8 +1,8 @@ -# Copyright 1999-2017 Gentoo Foundation +# Copyright 1999-2018 Gentoo Foundation # This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License. # https://creativecommons.org/licenses/by-sa/3.0/ Ebuild development quiz -Revision 1.16 - 01 December 2016 +Revision 1.17 - 02 September 2018 Answer in whatever length necessary for completeness. Support your answers @@ -66,14 +66,14 @@ docs: devmanual docs: devmanual -3. (a) What is repoman? When should it be used? How would you check for QA - problems with repoman? +3.a. What is repoman? When should it be used? How would you check for QA + problems with repoman? 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 ::gentoo? What should be in the commit message? +3.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 ::gentoo repository? What should be in the commit message? docs: devmanual, wiki @@ -89,47 +89,47 @@ docs: devmanual docs: devmanual -6. What steps are needed to remove a use flag from IUSE in an ebuild? +6. What steps are needed to remove a use flag from an ebuild? -docs: +docs: common sense -7. You're creating an ebuild. Unfortunately, the default 'emake +7. You are creating an ebuild. Unfortunately, the default 'emake DESTDIR="${D}" install' call causes numerous access violations. What are the best long-term and short-term solutions? docs: devmanual -8. You're creating an ebuild that needs a patch. The patch is +8. You are creating an ebuild that needs a patch. The patch is nontrivially large - bigger than 20 KiB. Where should the patch be kept? docs: devmanual -9. You're creating an ebuild for a package whose license does not match +9. You are creating an ebuild for a package whose license does not match any of the licenses in the 'licenses' directory. What is the proper course of action? docs: GLEPs, devmanual -10. (a) You wish to have an ebuild marked "stable," taking it out of - ~ARCH KEYWORDS. It's a library. What steps should be taken to do so? +10.a. You wish to have an ebuild marked "stable," taking it out of + ~ARCH KEYWORDS. It's a library. What steps should be taken to do so? docs: devmanual - (b) You wish to mark an ebuild "testing," putting it into ~ARCH - KEYWORDS. It was previously hard-masked in package.mask. - What should be done prior to doing so? +10.b. You wish to mark an ebuild "testing," putting it into ~ARCH + KEYWORDS. It was previously hard-masked in package.mask. + What should be done prior to doing so? docs: devmanual - (c) You wish to have an ebuild marked "stable." It is a popular - application, but no other ebuilds depend on it. - How would you handle it? +10.c. You wish to have an ebuild marked "stable." It is a popular + application, but no other ebuilds depend on it. + How would you handle it? docs: devmanual -11. What is the difference between different dependency classes (DEPEND and - RDEPEND)? When should each of them be used? Provide examples. +11. What is the difference between different dependency classes (DEPEND, + RDEPEND and BDEPEND)? When should each of them be used? Provide examples. docs: devmanual @@ -139,8 +139,11 @@ docs: devmanual docs: devmanual -13. You find a situation in which an eclass may be useful. What should - you do before implementing such an eclass? +13.a. You find a situation in which an eclass may be useful. What should + you do before implementing such an eclass? + +13.b. What is EXPORT_FUNCTIONS? How should it be used? + Provide examples of its usage. docs: devmanual @@ -168,8 +171,8 @@ docs: devmanual, PMS docs: devmanual -19. How do keywording policies for less often used arches like ia64 or - mips differ from the more common ones like amd64? +19. How do keywording and stabilization policies for less often used arches + like ia64 or mips differ from the more common ones like amd64? docs: devmanual |