diff options
author | 2022-01-18 18:14:24 +0200 | |
---|---|---|
committer | 2022-01-18 18:19:07 +0200 | |
commit | ece6111a1711766cb8738ac605eb820bf13cff68 (patch) | |
tree | fdb274225a0a172b980e42ad920d0996116c0afa | |
parent | ebuild-maintainer-quiz: group all license-related questions together (diff) | |
download | comrel-ece6111a1711766cb8738ac605eb820bf13cff68.tar.gz comrel-ece6111a1711766cb8738ac605eb820bf13cff68.tar.bz2 comrel-ece6111a1711766cb8738ac605eb820bf13cff68.zip |
ebuild-maintainer-quiz: add a new license question
- regarding writing ebuilds for go/rust etc programs.
Signed-off-by: Joonas Niilola <juippis@gentoo.org>
-rw-r--r-- | recruiters/quizzes/ebuild-maintainer-quiz.txt | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/recruiters/quizzes/ebuild-maintainer-quiz.txt b/recruiters/quizzes/ebuild-maintainer-quiz.txt index 5643f1d..6141a8c 100644 --- a/recruiters/quizzes/ebuild-maintainer-quiz.txt +++ b/recruiters/quizzes/ebuild-maintainer-quiz.txt @@ -225,13 +225,17 @@ docs: devmanual 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 +docs: devmanual 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? +21.h. You are writing an ebuild for a package written in either Rust or Go + programming language, how do you approach writing correct LICENSE value + in your ebuild? The main project is licensed as MIT. + *** PART ||| Code questions |