diff options
author | Joonas Niilola <juippis@gentoo.org> | 2022-01-18 16:23:13 +0200 |
---|---|---|
committer | Joonas Niilola <juippis@gentoo.org> | 2022-01-18 18:19:07 +0200 |
commit | fe763a82f46f1327d6a0f8f903dd8104c410e84d (patch) | |
tree | ff4840ed0e33ad3617d5a9eb4f94c66a9dcd5d63 | |
parent | ebuild-maintainer-quiz: combine questions regarding error handling (diff) | |
download | comrel-fe763a82f46f1327d6a0f8f903dd8104c410e84d.tar.gz comrel-fe763a82f46f1327d6a0f8f903dd8104c410e84d.tar.bz2 comrel-fe763a82f46f1327d6a0f8f903dd8104c410e84d.zip |
ebuild-maintainer-quiz: group all license-related questions together
- for consistency, and to avoid repetition in answers.
Signed-off-by: Joonas Niilola <juippis@gentoo.org>
-rw-r--r-- | recruiters/quizzes/ebuild-maintainer-quiz.txt | 70 |
1 files changed, 35 insertions, 35 deletions
diff --git a/recruiters/quizzes/ebuild-maintainer-quiz.txt b/recruiters/quizzes/ebuild-maintainer-quiz.txt index 3ab9c66..5643f1d 100644 --- a/recruiters/quizzes/ebuild-maintainer-quiz.txt +++ b/recruiters/quizzes/ebuild-maintainer-quiz.txt @@ -13,8 +13,8 @@ Consult your mentor if you're unable to locate answers. Do not discuss these questions and their answers in public. Do not publish or share any private conversation with your mentor or recruiter. -*** PART I Organizational structure questions +*** PART I Organizational structure questions 1. When is it appropriate to post to the following mailing lists: gentoo-core, gentoo-dev, gentoo-dev-announce, gentoo-project? Provide examples of topics @@ -51,8 +51,8 @@ docs: devmanual, GLEPs docs: wiki -*** PART II Ebuild technical/policy questions +*** PART II Ebuild technical/policy questions 1. You change a package's ebuild to install an init script. Previously, the package had no init script at all. @@ -107,94 +107,94 @@ docs: devmanual docs: devmanual -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? +9.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 -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? +9.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 -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? +9.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. List all available dependency classes (DEPEND, RDEPEND etc). How do they +10. List all available dependency classes (DEPEND, RDEPEND etc). How do they differ from each other? Provide examples of their uses. docs: devmanual -12. You wish to make a change to an ebuild, but you checked the commit +11. You wish to make a change to an ebuild, but you checked the commit messages and metadata.xml and it appears to be maintained by someone else. How should you proceed? docs: devmanual -13.a. You find a situation in which an eclass may be useful. What should +12.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? +12.b. What is EXPORT_FUNCTIONS? How should it be used? Provide examples of its usage. docs: devmanual -14. How can you verify an ebuild has correct run time dependencies +13. How can you verify an ebuild has correct run time dependencies (RDEPEND) for all installed binaries? Provide an example tool calls. docs: -15. How do you deal with a situation in which an ebuild tries to +14. 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 -16. Most configure scripts attempt to automatically determine +15. Most configure scripts attempt to automatically determine settings based on the host system. When should the ebuild specifically override settings? docs: devmanual -17. What is the EAPI version? How does it affect ebuilds and eclasses? +16. What is the EAPI version? How does it affect ebuilds and eclasses? docs: devmanual, PMS -18. What is the procedure for removing packages from the tree? +17. What is the procedure for removing packages from the tree? docs: devmanual -19. How do keywording and stabilization policies for less often used arches +18. How do keywording and stabilization policies for less often used arches like ppc64 or mips differ from the more common ones like amd64? docs: devmanual -20. You are adding a new major version to the tree that requires users to +19. 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 -21. What are sub-slots and their binding operators? What problem do they +20. What are sub-slots and their binding operators? What problem do they solve in gentoo and when should be used? Provide examples. docs: wiki, portage documentation -22.a. You are about to add a new package. How would you determine the correct +21.a. You are about to add a new package. How would you determine the correct LICENSE? What sources should be consulted for license information, and which take precedence? docs: devmanual -22.b. The package frobnicate has a 'COPYING' that exactly matches GPL-3. +21.b. 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 + +21.c. The package frobnicate has a 'COPYING' that exactly matches GPL-3. However, all the source files have the following copyright notice: @@ -207,13 +207,13 @@ docs: devmanual docs: devmanual -22.c. The package installs both frobnicate executable (licensed GPL-3+) +21.d. The package installs both frobnicate executable (licensed GPL-3+) and libfrobnicate shared library (licensed LGPL-2.1+). What should be the correct value of LICENSE for this package? docs: devmanual -22.d. The package installs frobnicate executable whose sources indicate GPL-3+ +21.e. The package installs frobnicate executable whose sources indicate GPL-3+ license. However, you notice that the build process creates a local static libport.a library that is used to build a part of frobnicate but is not meant to be installed. The sources of libport.a indicate @@ -221,19 +221,19 @@ docs: devmanual docs: devmanual -22.e. A MIT-licensed package includes a CDDL-licensed script. The script is +21.f. A MIT-licensed package includes a CDDL-licensed script. The script is not installed but it is used during build to generate a Makefile. What should be the value of LICENSE for this package? docs: common sense -22.f. A BSD-licensed package installs a frobnicate executable. However, after +21.g. A BSD-licensed package installs a frobnicate executable. However, after inspecting the package sources you notice that it uses a single source file whose license indicates GPL-2+. What would you do? What could be the LICENSE for this package? -*** PART ||| Code questions +*** PART ||| Code questions 1. You are writing an ebuild for the foomatic package. Upstream calls the current version "1.3-7b" (but this is _not_ a beta release). |