| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
- since the example keyserver has been shut down, and @gentoo.org UID keys
will only be made if a candidate will be recruited as a full developer.
Signed-off-by: Joonas Niilola <juippis@gentoo.org>
|
|
|
|
| |
Signed-off-by: Joonas Niilola <juippis@gentoo.org>
|
|
|
|
| |
Signed-off-by: Joonas Niilola <juippis@gentoo.org>
|
|
|
|
| |
Signed-off-by: Joonas Niilola <juippis@gentoo.org>
|
|
|
|
|
|
|
|
|
| |
- make it clearer it's not about supporting some ancient deprecating
GCC,
- try to hint there are scenarios when this check can be skipped
(suggested by sam).
Signed-off-by: Joonas Niilola <juippis@gentoo.org>
|
|
|
|
|
|
| |
- make it clear this question is about optional runtime dependencies.
Signed-off-by: Joonas Niilola <juippis@gentoo.org>
|
|
|
|
|
|
|
|
|
| |
This reverts commit 242b4cc7a1b82865b205973883c36137fcb06c79.
- needs a 2nd review round. If the candidate wasn't aware of these
docs and specs, they wouldn't get far to begin with.
Signed-off-by: Joonas Niilola <juippis@gentoo.org>
|
|
|
|
| |
Signed-off-by: Joonas Niilola <juippis@gentoo.org>
|
|
|
|
|
|
|
|
| |
- the candidate should be familiar with all of these before moving on
to technical & code questions.
Suggested-by: sam
Signed-off-by: Joonas Niilola <juippis@gentoo.org>
|
|
|
|
|
|
|
| |
- provide hints what we're looking for in a good answer.
Suggested-by: sam
Signed-off-by: Joonas Niilola <juippis@gentoo.org>
|
|
|
|
| |
Signed-off-by: Joonas Niilola <juippis@gentoo.org>
|
|
|
|
| |
Signed-off-by: Joonas Niilola <juippis@gentoo.org>
|
|
|
|
|
|
| |
- regarding writing ebuilds for go/rust etc programs.
Signed-off-by: Joonas Niilola <juippis@gentoo.org>
|
|
|
|
|
|
| |
- for consistency, and to avoid repetition in answers.
Signed-off-by: Joonas Niilola <juippis@gentoo.org>
|
|
|
|
| |
Signed-off-by: Joonas Niilola <juippis@gentoo.org>
|
|
|
|
|
|
|
|
|
| |
- expect the candidate to find all available dependency types, and
mention them in their answer,
- and so we don't have to keep updating the quiz everytime a new
*DEPEND support is added.
Signed-off-by: Joonas Niilola <juippis@gentoo.org>
|
|
|
|
|
|
|
|
| |
They have not been tracked properly recently.
With git it is really easier to go without formal revisioning
as all the history can be seen using the `git log` command.
Signed-off-by: Mikle Kolyada <zlogene@gentoo.org>
|
|
|
|
| |
Signed-off-by: Mikle Kolyada <zlogene@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
| |
ia64 is ~arch only for now
Signed-off-by: Mikle Kolyada <zlogene@gentoo.org>
|
|
|
|
|
|
|
| |
Clarify that we want the candidate to demonstrate the knowledge of
ebuild helper functions regarding the topic as well.
Signed-off-by: Göktürk Yüksek <gokturk@gentoo.org>
|
|
|
|
| |
Signed-off-by: Amy Liffey <amynka@gentoo.org>
|
|
|
|
| |
Signed-off-by: Mikle Kolyada <zlogene@gentoo.org>
|
|
|
|
| |
Signed-off-by: Mikle Kolyada <zlogene@gentoo.org>
|
|
|
|
| |
Signed-off-by: Mikle Kolyada <zlogene@gentoo.org>
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
- Sync numbering style with the end-quiz
- wording fix for Q3b
- generalize Q6
- Q7-Q9 style fix
- Ask about BDEPEND as well in Q11
- Add Q13b about EXPORT_FUNCTIONS (bug #601862)
- Generalize Q19 (add stabilization)
|
|
|
|
|
|
|
|
| |
- add LibreSSL and bump Q2 to the EAPI=7
- remove question about basic shell tools (useless in the scope of Gentoo)
- remove question about /var
- remove Q6.a as there is no practical use of it
- update revision and copyright
|
| |
|
|
|
|
|
|
| |
Reverse the GCC question to avoid suggesting that the package builds
only with GCC -- i.e. make it say it does not build with old gcc. This
could naturally be used to check user's awareness of other compilers.
|
|
|
|
|
| |
They are quite related, so it seems more reasonable to have them
combined. Furthermore, it reduces the apparent question number!
|
|
|
|
|
|
|
| |
Avoid using the term 'local scope' as it is unclear and may suggest bash
function scope (with the function being called in global scope anyway).
The PMS uses talks only of 'global scope'. Use 'phase scope' as a more
precise antonym.
|
|
|
|
|
|
|
|
|
|
| |
Make the question a little more tricky by suggesting that OpenSSL is
being used and modernizing SSL into TLS. This requires the recruit to
figure out the appropriate USE flag, and makes sure he won't choose
USE=openssl.
Also, make it clear that the optional dependency is enabled/disabled at
build time, and not is a pure build time dependency.
|
| |
|
|
|
|
| |
Reported-by: M. J. Everitt <m.j.everitt@iee.org>
|
| |
|
|
|
|
| |
Reported-By: Horea Christian <horea.christ@yandex.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Attempt to improve the ebuild quiz further:
- expand and clarify a few of the questions,
- add a variant of q1 for dependency changes,
- merge q11 into q3 -- both are about committing a user-submitted
ebuild, so it makes sense to ask both at the same time,
- expand q12 (now q11) to all dependency types,
- remove the mention of ChangeLogs since they no longer affect the git
repository used by developers.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Attempt to improve the non-ebuild developer quiz:
- explicitly request documentation links along answers,
- try to clarify the questions, request specific details,
- merge project-related questions since they overlap,
- reorder and split the question so that the organizational part matches
the ebuild developer quiz.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Devmanual now includes documentation about how projects are created
and removed.
|
|
|
|
|
| |
Devmanual now includes documentation about how projects are created
and removed.
|
|
|
|
| |
Signed-off-by: Justin Lecher <jlec@gentoo.org>
|