diff options
author | 2020-10-09 16:22:52 +0300 | |
---|---|---|
committer | 2020-10-09 17:11:40 +0300 | |
commit | 2ee0456381610a2fdb1eaf09f60f43668f7d12bb (patch) | |
tree | 66ceec1958c8c1b33c5a4f767e0d20910fdbf857 | |
parent | ebuild-maintainer quiz: change ia64 → ppc64 (diff) | |
download | comrel-2ee0456381610a2fdb1eaf09f60f43668f7d12bb.tar.gz comrel-2ee0456381610a2fdb1eaf09f60f43668f7d12bb.tar.bz2 comrel-2ee0456381610a2fdb1eaf09f60f43668f7d12bb.zip |
ebuild-maintainer.quiz: remove openrc-specific questions
RATIONALE:
Gentoo GNU/Linux has always been about choice.
In the mean time we have always had good support
for systemd. Quizzes should not prefer one init
system over another. Perspective developers must
not be forced to answer questions which are
against their philosophy. OpenRC features must be
documented upstream.
Signed-off-by: Mikle Kolyada <zlogene@gentoo.org>
-rw-r--r-- | recruiters/quizzes/ebuild-maintainer-quiz.txt | 47 |
1 files changed, 17 insertions, 30 deletions
diff --git a/recruiters/quizzes/ebuild-maintainer-quiz.txt b/recruiters/quizzes/ebuild-maintainer-quiz.txt index 5a25289..74a7e02 100644 --- a/recruiters/quizzes/ebuild-maintainer-quiz.txt +++ b/recruiters/quizzes/ebuild-maintainer-quiz.txt @@ -1,11 +1,11 @@ # Copyright 1999-2019 Gentoo Authors # Copyright 2016-2019 Amy Liffey -# Copyright 2016-2019 Mikle Kolyada +# Copyright 2016-2020 Mikle Kolyada # This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License. # https://creativecommons.org/licenses/by-sa/3.0/ Ebuild maintainer quiz -Revision 2.22.8 - 7 January 2019 +Revision 2.22.9 - 9 October 2020 Answer in whatever length necessary for completeness. Support your answers with documentation links but avoid redundant citation. @@ -311,44 +311,31 @@ docs: devmanual docs: devmanual - -7. You're writing an ebuild and init script for a server application - that needs networking to be available when started and can also - use a system logger if one is available. How should this be - written in the init script? - -docs: devmanual - -8. What is the 'Gentoo way' of allowing the user to pass other options - to the previously mentioned server application? - -docs: devmanual - -9. What is the 'Gentoo way' of globally setting environment variables +7. What is the 'Gentoo way' of globally setting environment variables for all users? How is this accomplished in ebuilds? docs: devmanual -10. Which directory should manual (man) pages be in and how should they +8. Which directory should manual (man) pages be in and how should they be installed from an ebuild? docs: PMS -11. On Gentoo Linux systems, what is the purpose of /usr/local/bin? +9. On Gentoo Linux systems, what is the purpose of /usr/local/bin? docs: devmanual -12. When should you use || die "msg" with commands/functions? +10. When should you use || die "msg" with commands/functions? Could || die always be moved inside those functions/commands? docs: devmanual -13.a. You are committing a new package to the tree. What will you have in +11.a. You are committing a new package to the tree. What will you have in the KEYWORDS variable? docs: devmanual -13.b. You are bumping foomatic's ebuild from version 1.2 to version +11.b. You are bumping foomatic's ebuild from version 1.2 to version 1.3. The new release contains bugfixes and new functionality. The current KEYWORDS for 1.2 are "x86 sparc ~mips amd64" -- what will KEYWORDS be for @@ -356,7 +343,7 @@ docs: devmanual docs: devmanual -13.c. You are bumping foomatic's ebuild from version 1.3 to 1.4. The +11.c. You are bumping foomatic's ebuild from version 1.3 to 1.4. The new release extends functionality and introduces a new dependency on libfnord version 1.2 or later. The KEYWORDS for foomatic-1.3 are "x86 sparc ~mips amd64" @@ -365,7 +352,7 @@ docs: devmanual docs: devmanual -13.d. You are bumping foomatic's ebuild from version 1.4 to 1.5. This +11.d. You are bumping foomatic's ebuild from version 1.4 to 1.5. This release introduces new optional support for the libgerbil library, which you are controlling via the gerbil global USE flag. Unfortunately libgerbil is full of code which @@ -374,33 +361,33 @@ docs: devmanual docs: devmanual -13.e. You are bumping foomatic's ebuild from version 1.5 to version +11.e. You are bumping foomatic's ebuild from version 1.5 to version 2.0. This new version is a massive rewrite which introduces huge changes to the build system, the required libraries and how the code works. What will you do for KEYWORDS here? docs: devmanual -14. Your package fails to build with older versions of GCC (e.g. GCC < 4.7). +12. Your package fails to build with older versions of GCC (e.g. GCC < 4.7). How do you ensure that the user uses an appropriate compiler to build the package? Under which circumstances should you avoid this check and how? docs: devmanual -15. When should USE flags be used? What are the cases where they should be +13. When should USE flags be used? What are the cases where they should be avoided? Consider the following examples. Explain what is wrong in them and how would you improve them. docs: devmanual, common sense -15.a. A large C++ application with long build time has: +13.a. A large C++ application with long build time has: # libcxx can be optionally used at run time via -stdlib=libc++ IUSE="libcxx" DEPEND="" RDEPEND="libcxx? ( dev-libs/libcxx )" -15.b. A large package with long build time has: +13.b. A large package with long build time has: inherit bash-completion-r1 IUSE="bash-completion" @@ -410,7 +397,7 @@ docs: devmanual, common sense use bash-completion && dobashcomp contrib/bash-completion/foo } -15.c. A package unconditionally installs 'foobar' executable which links +13.c. A package unconditionally installs 'foobar' executable which links to libbar. The ebuild maintainer wanted to make it optional. He used the following code: @@ -425,7 +412,7 @@ docs: devmanual, common sense fi } -15.d. A package has numerous configure switches which control a number +13.d. A package has numerous configure switches which control a number of optional features. All of them are enabled by default. They do not have any external dependencies, and do not affect the package size significantly. The ebuild author has added over 20 local USE |