1 |
Dear Community, |
2 |
|
3 |
First of all, please do not take this personally. I don't want to |
4 |
attack any member of the games team or the team in general. I respect |
5 |
their experience and long-term contribution to Gentoo. However, |
6 |
I strongly disagree with the policy games team has established and I |
7 |
believe that their actions do not serve the best interest of Gentoo. |
8 |
|
9 |
I am therefore going to propose this request to the next Council. Since |
10 |
this will likely require a fair amount of prior discussion, I would |
11 |
like to start it already, hopefully reaching at least some point before |
12 |
the appropriate Council meeting. |
13 |
|
14 |
|
15 |
I would like to ask the Council to abolish the following policies that |
16 |
have been established by the games team: |
17 |
|
18 |
1. that the games team has authority over the actual maintainers |
19 |
on every game ebuild, |
20 |
|
21 |
2. that every ebuild has to inherit games.eclass as the last eclass |
22 |
inherited [1], even if it actually increases the ebuild size rather |
23 |
than helping, |
24 |
|
25 |
3. that games must adhere to games team-specific install locations |
26 |
and ownership rules, shortly listed in [2]. |
27 |
|
28 |
More specifically, I would like the games to be 'freed' from the games |
29 |
team monopoly and treated like every other package. More specifically, |
30 |
I believe that: |
31 |
|
32 |
i. games should be maintained by their respective maintainers, |
33 |
and games team (if any) should help rather than overriding their |
34 |
decisions, |
35 |
|
36 |
ii. that the games.eclass should be deprecated and likely disabled |
37 |
in the next EAPI since wrapping phases and helper functions makes it |
38 |
close to base.eclass in design, |
39 |
|
40 |
iii. that the games group along with the game-specific install tree |
41 |
should be deprecated and phased out. Games should be installed alike |
42 |
any other applications. |
43 |
|
44 |
|
45 |
I feel like the games team is more focused on keeping the 'status |
46 |
quo' than working on improving the experience of Gentoo users. |
47 |
The problems with current game install design have been pointed out |
48 |
multiple times, and the suggestions were either ignored by the team or |
49 |
refused, sometimes with strong words. In fact, the team's own decisions |
50 |
are creating further issues that they afterwards need to work around. |
51 |
|
52 |
The most notable issues with the specific use of games group include: |
53 |
|
54 |
a. nethack security issue [3] that is purely Gentoo-specific, and is |
55 |
open with no action from games since 2006, |
56 |
|
57 |
b. multiple game ebuilds being unable to access files installed by |
58 |
other game ebuilds that are worked around with dangerous |
59 |
RESTRICT=userpriv [4,5,6]. |
60 |
|
61 |
Moreover, the eclass is purely suited for autotools-based ebuilds. |
62 |
The policy enforced by the team makes it very hard to create proper |
63 |
ebuilds for other build systems, often requiring redeclaration of all |
64 |
phase functions (to restore the proper eclass) and heavy patching of |
65 |
install locations. |
66 |
|
67 |
|
68 |
The number of inconveniences, lack of replies (lack of time?) has |
69 |
resulted in multiple games being spread throughout various overlays. |
70 |
I think the gamerlay project [7] is most notable. Sadly, this results |
71 |
in even worse quality of games in Gentoo. |
72 |
|
73 |
I believe that the policy needs to change. While I respect the members |
74 |
of games team, I don't think they should be allowed to prevent other |
75 |
developers from committing game ebuilds, and I don't agree with keeping |
76 |
the 'status quo' of games.eclass for the sake of keeping it while |
77 |
the issues outweigh the benefit (it is actually negotiable whether |
78 |
there's any). |
79 |
|
80 |
I would like to ask the Community for their opinion on this issue. |
81 |
When the new Council term starts, I will add the issue to the agenda. |
82 |
Unless the games team decides to give up their policies and allow |
83 |
developers to work on cleaning up games before that. |
84 |
|
85 |
|
86 |
[1]:http://www.gentoo.org/proj/en/desktop/games/games-ebuild-howto.xml#doc_chap3 |
87 |
[2]:http://www.gentoo.org/proj/en/desktop/games/games-ebuild-howto.xml#doc_chap4 |
88 |
[3]:https://bugs.gentoo.org/show_bug.cgi?id=125902 |
89 |
[4]:https://bugs.gentoo.org/show_bug.cgi?id=112898 |
90 |
[5]:https://bugs.gentoo.org/show_bug.cgi?id=419331 |
91 |
[6]:https://bugs.gentoo.org/show_bug.cgi?id=516576 |
92 |
[7]:https://git.overlays.gentoo.org/gitweb/?p=proj/gamerlay.git;a=summary |
93 |
|
94 |
-- |
95 |
Best regards, |
96 |
Michał Górny |