ebuild-quiz: Unify indentation with dev-quiz

1 files changed, 75 insertions, 75 deletions

diff --git a/recruiters/quizzes/ebuild-quiz.txt b/recruiters/quizzes/ebuild-quiz.txt
index 8d04d79..6ce9f36 100644
--- a/recruiters/quizzes/ebuild-quiz.txt
+++ b/recruiters/quizzes/ebuild-quiz.txt
@@ -49,160 +49,160 @@ docs: wiki
 
 *** 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.
-	Is a revision bump necessary? Why? What about when adding a patch?
+1. You change a package's ebuild to install an init script. Previously,
+   the package had no init script at all.
+   Is a revision bump necessary? Why? What about when adding a patch?
 
 docs: devmanual
 
-2.	A user submits a "live" VCS (git, svn ...) ebuild. What would be a preferable
-	alternative to such an ebuild?
+2. A user submits a "live" VCS (git, svn ...) ebuild. What would be a preferable
+   alternative to such an ebuild?
 
 docs: devmanual
 
-3.	(a) What is repoman? How would you check for QA problems with
-	repoman?
+3. (a) What is repoman? How would you check for QA problems with
+   repoman?
 
 docs: devmanual, wiki
 
-	(b) A user submits a brand-new ebuild for a new package. What are the
-	proper steps (including repoman commands) to take to add
-	this ebuild to the tree?
+   (b) A user submits a brand-new ebuild for a new package. What are the
+   proper steps (including repoman commands) to take to add
+   this ebuild to the tree?
 
 docs: devmanual, wiki
 
-4.	A user submits an ebuild that has numerous technical problems and
-	violates policy. How would you handle that situation?
+4. A user submits an ebuild that has numerous technical problems and
+   violates policy. How would you handle that situation?
 
 docs: devmanual
 
-5.	You have a set of new ebuilds that could potentially benefit
-	from a global USE flag. What steps should be taken before
-	a new USE flag is implemented? What should be done if the
-	USE flag only applies to a single package?
+5. You have a set of new ebuilds that could potentially benefit
+   from a global USE flag. What steps should be taken before
+   a new USE flag is implemented? What should be done if the
+   USE flag only applies to a single package?
 
 docs: devmanual
 
-6.	What steps are needed to remove a use flag from IUSE in an ebuild?
+6. What steps are needed to remove a use flag from IUSE in an ebuild?
 
 docs:
 
-7.	You're creating an ebuild. Unfortunately, the ebuild's 'make install'
-	target causes numerous access violations. What is the best
-	course of action to take to have a clean, straightforward
-	ebuild?
+7. You're creating an ebuild. Unfortunately, the ebuild's 'make install'
+   target causes numerous access violations. What is the best
+   course of action to take to have a clean, straightforward
+   ebuild?
 
 docs: devmanual
 
-8.	You're creating an ebuild that needs a patch. The patch is
-	nontrivially large - bigger than 20kbytes. Where should
-	the patch be kept?
+8. You're creating an ebuild that needs a patch. The patch is
+   nontrivially large - bigger than 20kbytes. Where should
+   the patch be kept?
 
 docs: devmanual
 
-9.	You're creating an ebuild that has its own license - one that
-	doesn't exist in /usr/portage/licenses/. What is the proper
-	course of action?
+9. You're creating an ebuild that has its own license - one that
+   doesn't exist in /usr/portage/licenses/. 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?
+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?
 
 docs: devmanual
 
-	(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?
+    (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
 
-	(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?
+    (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.	You're committing a user-submitted ebuild. What should be in the
-	initial commit message?
+11. You're committing a user-submitted ebuild. What should be in the
+    initial commit message?
 
 docs: devmanual
 
-12.	What is the difference between DEPEND and RDEPEND?
+12. What is the difference between DEPEND and RDEPEND?
 
 docs: devmanual
 
-13.	You wish to make a change to an ebuild, but you checked
-	ChangeLogs, commit messages and metadata.xml and it appears to be 
-	maintained by someone else. How should you proceed?
+13. You wish to make a change to an ebuild, but you checked
+    ChangeLogs, commit messages and metadata.xml and it appears to be 
+    maintained by someone else. How should you proceed?
 
 docs: devmanual
 
-14.	You find a situation in which an eclass may be useful. What should
-	you do before implementing such an eclass?
+14. 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
-	(RDEPEND) for all installed binaries?
+15. How can you verify an ebuild has correct run time dependencies
+    (RDEPEND) for all installed binaries?
 
 docs:
 
-16.	How do you deal with a situation in which an ebuild wishes to
-	install a file already installed by another package?
+16. How do you deal with a situation in which an ebuild wishes to
+    install a file already installed by another package?
 
 docs: devmanual
 
-17.	Most configure scripts attempt to automatically determine
-	settings based on the host system. When should the ebuild
-	specifically override settings?
+17. 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 EAPI?
+18. What is EAPI?
 
 docs: devmanual, PMS
 
-19.	What is the procedure for removing packages from the tree?
+19. 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
-	mips differ from the more common ones like amd64?
+20. 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
-	follow an upgrade guide. How will you communicate this to the users?
+21. 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
 
 
 *** Please also submit the following information:
 
-*	Please make sure your OpenPGP public keyblock is available on the keyserver network 
-	hkp://pool.sks-keyservers.net and provide the fingerprint of it below
-	You should sign your quizzes with your key
-	https://wiki.gentoo.org/wiki/Project:Gentoo-keys/Generating_GLEP_63_based_OpenPGP_keys
-	https://wiki.gentoo.org/wiki/GnuPG
+* Please make sure your OpenPGP public keyblock is available on the keyserver network 
+  hkp://pool.sks-keyservers.net and provide the fingerprint of it below
+  You should sign your quizzes with your key
+  https://wiki.gentoo.org/wiki/Project:Gentoo-keys/Generating_GLEP_63_based_OpenPGP_keys
+  https://wiki.gentoo.org/wiki/GnuPG
 
-*	SSH public key (if you do not have one, please create one)
-	https://wiki.gentoo.org/wiki/Project:Infrastructure/SSH_Key_Guide
-	If you don't paste your key inline, make sure it's signed by your
-	gpg key.
+* SSH public key (if you do not have one, please create one)
+  https://wiki.gentoo.org/wiki/Project:Infrastructure/SSH_Key_Guide
+  If you don't paste your key inline, make sure it's signed by your
+  gpg key.
 
-*	Date of birth
+* Date of birth
 
-*	Where do you live (Town/City, Country)
+* Where do you live (Town/City, Country)
 
-*	What are your programming/scripting skills, if applicable?
+* What are your programming/scripting skills, if applicable?
 
-*	What other areas are you experienced in?
+* What other areas are you experienced in?
 
-*	What other projects have you contributed to, if any?
+* What other projects have you contributed to, if any?
 
-*	Tell us about yourself. This doesn't need to be strictly
-	computer-relevant; things like where you're from,
-	hobbies, job, family, interests... This information will be used
-	for your public new developer announcement so please mention if
-	something should not be part of that.
+* Tell us about yourself. This doesn't need to be strictly
+  computer-relevant; things like where you're from,
+  hobbies, job, family, interests... This information will be used
+  for your public new developer announcement so please mention if
+  something should not be part of that.