Gentoo Archives: gentoo-project

From: Arfrever Frehtes Taifersar Arahesis <arfrever.fta@×××××.com>
To: Gentoo Project <gentoo-project@l.g.o>
Subject: [gentoo-project] Questions for candidates for Gentoo Council 2013/2014
Date: Mon, 01 Jul 2013 18:54:53
Message-Id: 201307012054.06728.Arfrever.FTA@gmail.com
1 All candidates for Gentoo Council 2013/2014 are asked to answer the following
2 technical questions, since Gentoo Council 2013/2014 will vote on at least
3 some of relevant propositions.
4
5 (Non-candidates are asked to not start any discussions in this thread.)
6
7 01. What interval (in months) between introductions of new EAPIs do you prefer?
8
9 02. Will you vote for moving system packages (gcc, glibc etc.) to EAPI >=3?
10
11 03. Will you vote for moving system packages (gcc, glibc etc.) to EAPI >=4?
12
13 04. Will you vote for moving system packages (gcc, glibc etc.) to EAPI >=5?
14
15 # EAPIs 1 and 2 are currently deprecated in gentoo-x86.
16 # Deprecation of an EAPI in gentoo-x86 has no effect to what is supported by
17 # package managers and what is described in PMS.
18
19 05. Will you vote for deprecation of EAPI 0 in gentoo-x86?
20
21 06. Will you vote for deprecation of EAPI 3 in gentoo-x86?
22
23 07. Will you vote for deprecation of EAPI 4 in gentoo-x86?
24
25 08. Will you vote for including support for version ranges in EAPI 6
26 (assuming that a patch is available for Portage)?
27
28 09. Will you vote for including support for USE-flag-dependent slots in EAPI 6
29 (assuming that a patch is available for Portage)?
30
31 10. Will you vote for including support for package.mask, package.use
32 and {,package.}use{,.stable}.{force,mask} directories in EAPI 6
33 (assuming that a patch is available for Portage)?
34
35 11. Will you vote for providing master_repositories(), repository_path(),
36 available_eclasses(), eclass_path() and license_path() functions in EAPI 6
37 (assuming that a patch is available for Portage)?
38
39 12. Will you vote for removing PORTDIR and ECLASSDIR variables in EAPI 6
40 (assuming that a patch is available for Portage)?
41
42 13. Will you vote for including support for automatic unpack dependencies
43 (configurable in single location in repository) in EAPI 6
44 (assuming that a patch is available for Portage)?
45
46 14. Will you vote for allowing bash-4.2 features in EAPI 6
47 (assuming that a patch is available for Portage)?
48
49 15. Will you vote for enabling globstar shell option by default in EAPI 6
50 (assuming that a patch is available for Portage)?
51
52 16. Will you vote for providing REPOSITORY variable in EAPI 6
53 (assuming that a patch is available for Portage)?
54
55 17. Will you vote for including support for repository dependencies in EAPI 6
56 (assuming that a patch is available for Portage)?
57
58 18. Will you vote for including support for repository-specific
59 package.use and {,package.}use{,.stable}.{force,mask} in EAPI 6
60 (assuming that a patch is available for Portage)?
61
62 19. Will you vote for including support for optional run-time dependencies
63 controlled by run-time-switchable USE flags (GLEP 62) in EAPI 6
64 (assuming that a patch is available for Portage)?
65
66 20. Will you vote for including support for host/target-specific dependencies in EAPI 6
67 (assuming that a patch is available for Portage)?
68
69 21. Will you vote for including support for crosscompilation-specific
70 dependencies in EAPI 6
71 (assuming that a patch is available for Portage)?
72
73 22. Will you vote for including support for DEPENDENCIES variable with labels in EAPI 6
74 (assuming that a patch is available for Portage)?
75
76 23. Will you vote for including support for labels in RESTRICT variable in EAPI 6
77 (assuming that a patch is available for Portage)?
78
79 24. Will you vote for exporting XDG_CACHE_HOME, XDG_CONFIG_HOME, XDG_DATA_HOME
80 and XDG_RUNTIME_DIR variables (with useful values) in EAPI 6
81 (assuming that a patch is available for Portage)?
82
83 25. Will you vote for including support for unique subslots for live ebuilds in EAPI 6
84 (assuming that a patch is available for Portage)?
85
86 26. Will you vote for including support for transitive subslots in EAPI 6
87 (assuming that a patch is available for Portage)?
88
89 27. Will you vote for including support for subslot dictionaries in EAPI 6
90 (assuming that a patch is available for Portage)?
91
92 28. Will you vote for including support for ico, svg, xhtml and xml files in
93 dohtml in EAPI 6
94 (assuming that a patch is available for Portage)?
95
96 29. Will you vote for disallowing diropts(), docompress(), exeopts(), insopts(),
97 keepdir(), libopts(), use(), use_enable(), use_with(), useq(), usev() and usex()
98 functions in global scope in EAPI 6
99 (assuming that a patch is available for Portage)?
100
101 30. Will you vote for including support for src_fetch() function in EAPI 6
102 (assuming that a patch is available for Portage)?
103
104 31. Will you vote for including support for "." characters in package names in EAPI 6
105 (assuming that a patch is available for Portage)?
106
107 32. Will you vote for including support for "." characters in USE flags in EAPI 6
108 (assuming that a patch is available for Portage)?
109
110 --
111 Arfrever Frehtes Taifersar Arahesis

Attachments

File name MIME type
signature.asc application/pgp-signature

Replies