diff options
author | 2017-01-08 16:54:07 +0100 | |
---|---|---|
committer | 2017-01-08 16:54:11 +0100 | |
commit | e72ebeb36bfe021eafc84f7f866455a80446e7e4 (patch) | |
tree | ba59aeca7f8128f25f3caa7d658c4b2a88a9b51a | |
parent | ebuild-quiz: remove pdepend (diff) | |
download | comrel-e72ebeb36bfe021eafc84f7f866455a80446e7e4.tar.gz comrel-e72ebeb36bfe021eafc84f7f866455a80446e7e4.tar.bz2 comrel-e72ebeb36bfe021eafc84f7f866455a80446e7e4.zip |
ebuild-quiz: reorder numbers
Reported-By: Horea Christian <horea.christ@yandex.com>
-rw-r--r-- | recruiters/quizzes/ebuild-quiz.txt | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/recruiters/quizzes/ebuild-quiz.txt b/recruiters/quizzes/ebuild-quiz.txt index 2a93fd3..8d28892 100644 --- a/recruiters/quizzes/ebuild-quiz.txt +++ b/recruiters/quizzes/ebuild-quiz.txt @@ -137,41 +137,41 @@ docs: devmanual docs: devmanual -14. You find a situation in which an eclass may be useful. What should +13. You find a situation in which an eclass may be useful. What should you do before implementing such an eclass? docs: devmanual -15. How can you verify an ebuild has correct run time dependencies +14. How can you verify an ebuild has correct run time dependencies (RDEPEND) for all installed binaries? Provide an example tool calls. docs: -16. How do you deal with a situation in which an ebuild tries to +15. How do you deal with a situation in which an ebuild tries to install a file that is already installed by another package? docs: devmanual -17. Most configure scripts attempt to automatically determine +16. Most configure scripts attempt to automatically determine settings based on the host system. When should the ebuild specifically override settings? docs: devmanual -18. What is the EAPI version? How does it affect ebuilds and eclasses? +17. What is the EAPI version? How does it affect ebuilds and eclasses? docs: devmanual, PMS -19. What is the procedure for removing packages from the tree? +18. What is the procedure for removing packages from the tree? docs: devmanual -20. How do keywording policies for less often used arches like ia64 or +19. How do keywording policies for less often used arches like ia64 or mips differ from the more common ones like amd64? docs: devmanual -21. You are adding a new major version to the tree that requires users to +20. You are adding a new major version to the tree that requires users to follow an upgrade guide. How will you communicate this to the users? docs: GLEPs |