diff options
| -rw-r--r-- | recruiters/quizzes/end-quiz.txt | 30 |
1 files changed, 13 insertions, 17 deletions
diff --git a/recruiters/quizzes/end-quiz.txt b/recruiters/quizzes/end-quiz.txt index 3ecf90c..e5eefe6 100644 --- a/recruiters/quizzes/end-quiz.txt +++ b/recruiters/quizzes/end-quiz.txt @@ -93,52 +93,48 @@ docs: devmanual docs: devmanual -8. Why are 'head -5' and 'tail -5' bad? What should be used instead? - -docs: - -9. You're writing an ebuild and init script for a server application +8. 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 -10. What is the 'Gentoo Way' of allowing the user to pass other options +9. What is the 'Gentoo Way' of allowing the user to pass other options to the previously mentioned server application? docs: devmanual -11. What is the 'Gentoo Way' of globally setting environment variables +10. What is the 'Gentoo Way' of globally setting environment variables for all users? docs: devmanual -12. What directory should be used for application-generated +11. What directory should be used for application-generated non-temporary data? docs: devmanual -13. Which directory should manual (man) pages be in and how should they +12. Which directory should manual (man) pages be in and how should they be installed from an ebuild? docs: PMS -14. On Gentoo Linux systems, what is the purpose of /usr/local/bin? +13. On Gentoo Linux systems, what is the purpose of /usr/local/bin? docs: devmanual -15. When should you use || die "msg" with commands/functions? +14. When should you use || die "msg" with commands/functions? Could || die always be moved inside those functions/commands? docs: devmanual -16. You are committing a new package to the tree. What will you have in +15. You are committing a new package to the tree. What will you have in the KEYWORDS variable? docs: devmanual -17. You are bumping foomatic's ebuild from version 1.2 to version +16. 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 @@ -146,7 +142,7 @@ docs: devmanual docs: devmanual -18. You are bumping foomatic's ebuild from version 1.3 to 1.4. The +17. 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" @@ -155,7 +151,7 @@ docs: devmanual docs: devmanual -19. You are bumping foomatic's ebuild from version 1.4 to 1.5. This +18. 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 @@ -164,14 +160,14 @@ docs: devmanual docs: devmanual -20. You are bumping foomatic's ebuild from version 1.5 to version +19. 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 -21. Your package only builds with newer gcc (e.g. >gcc-4.7). +20. Your package only builds with newer 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? |