Gentoo Archives: gentoo-dev

From: "Michał Górny" <mgorny@g.o>
To: Daniel Campbell <zlg@g.o>
Cc: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] [QA] Official support for migrating ebuilds out of games.eclass
Date: Thu, 30 Jun 2016 08:00:25
Message-Id: 20160630071121.2efd4b14.mgorny@gentoo.org
In Reply to: Re: [gentoo-dev] [QA] Official support for migrating ebuilds out of games.eclass by Daniel Campbell
1 On Wed, 29 Jun 2016 15:47:43 -0700
2 Daniel Campbell <zlg@g.o> wrote:
3
4 > On 06/29/2016 10:11 AM, Michał Górny wrote:
5 > > Hello, everyone.
6 > >
7 > > Over half a year has passed since Council decided upon the fate of
8 > > games in Gentoo. Over that period, the games team has neither showed
9 > > any will to respect the Council decisions, nor officially appealed to
10 > > them.
11 > >
12 > > For this reason, the QA team would like to officially start supporting
13 > > the migration of ebuilds out of games.eclass. Any developer wishing to
14 > > help is more than welcome to take any games.eclass ebuild, bump its
15 > > revision and remove the games.eclass-specific bits from it. Updating to
16 > > EAPI 6 would also be welcome. A short update guide is provided at
17 > > the end of mail.
18 > >
19 > > Please note that since this is considered a matter of QA action with
20 > > a long waiting period, no explicit approval from games team is
21 > > necessary to commit the conversion, nor games team is allowed to reject
22 > > or revert such commits as long as they are valid.
23 > >
24 > > If you need any help doing that and the games team refuses to provide
25 > > it, please do not hesitate to contact me or ask in #gentoo-qa. If you
26 > > are interested in helping out with games, feel free to join games team
27 > > since it still lacks new members.
28 > >
29 > > Thank you for all the help.
30 > >
31 > >
32 > > Migration notes
33 > > ---------------
34 > >
35 > > TL;DR: nothing special required, remove games.eclass and all
36 > > unnecessary games.eclass customization, and follow upstream. Make sure
37 > > not to break stuff.
38 > >
39 > >
40 > > The Council decisions can be summarized the following way:
41 > >
42 > > 1. The 'games' group, formerly used to control access to games, must
43 > > not be used. Games should be executable for all users like any other
44 > > program [1].
45 > >
46 > > 1a. For score files and similar writable shared data, the 'gamestat'
47 > > group (enewgroup gamestat 36) can be used. The old 'games' group is not
48 > > appropriate since sysadmins were expected to add users to it which
49 > > defeated its purpose.
50 > >
51 > > 2. Gentoo path customization for games must be removed and regular
52 > > install locations (without explicit control via GAMES_* variables)
53 > > should be used [2]:
54 > >
55 > > 2a. /usr/games and /etc/games directories are forbidden,
56 > >
57 > > 2b. /usr/share/games can be used for data if that directory is used
58 > > upstream,
59 > >
60 > > 2c. /var/games can be used for shared writable data.
61 > >
62 > >
63 > > This is mostly achieved through removing games.eclass inherit,
64 > > customization specific to it and replacing the helpers with generic PMS
65 > > helpers (e.g. egamesconf -> econf, dogamesbin -> dobin).
66 > > The 'gamesowners', 'gamesperms', 'prepgamesdirs' calls should be
67 > > removed altogether.
68 > >
69 > > In some cases it will also be beneficial to remove patching added to
70 > > support non-standard locations.
71 > >
72 > > Please remember to always rev-bump and not edit in place, to ensure
73 > > proper upgrade. When dealing with dependencies, please make sure to
74 > > check if the package does not rely on dependency installing data in
75 > > a specific location. If that is the case, then you need to use
76 > > appropriate >= deps to ensure clean upgrade.
77 > >
78 > > If you would like to report bugs requesting games.eclass removal,
79 > > please make them block the tracker [3].
80 > >
81 > >
82 > > [1]:https://projects.gentoo.org/council/meeting-logs/20151011-summary.txt
83 > > [2]:https://projects.gentoo.org/council/meeting-logs/20151213-summary.txt
84 > > [3]:https://bugs.gentoo.org/show_bug.cgi?id=574082
85 > >
86 > I'm glad to see some reach-out here and taking responsibility for
87 > decisions. However, what does the QA team have to say about systems that
88 > want games on other media (such as an SSD or separate HDD), or wish to
89 > restrict the use of games on their system to certain accounts?
90 >
91 > Bumping EAPI won't magically allow those to happen, and removing the
92 > eclass *will* break those use cases. What's the "blessed" way to do those?
93
94 If you want to do custom stuff, you're on your own. There are tricks to
95 do that (package.env, bashrc). Don't expect developers to patch packages
96 to satisfy your corner case.
97
98 --
99 Best regards,
100 Michał Górny
101 <http://dev.gentoo.org/~mgorny/>

Replies