From: "M.B." <tomboy64@sina.cn>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] games.eclass policy
Date: Sun, 7 Feb 2016 11:38:27 +0100 [thread overview]
Message-ID: <20160207113827.314d5bf0@hatshepsut> (raw)
Hello folks.
While hacking away on a new ebuild I came across the issue that
games.eclass apparently got banned from future use. The only references
I was able to dig up (apart from helpful people on IRC), were
https://bugs.gentoo.org/show_bug.cgi?id=566498 (games.eclass: use of
games group needs to be removed wrt 20151011 Council meeting)
and
https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Meeting_Summaries#Games_team_policies_issue
(A mere deprecation notice).
In contrast, a simple "grep deprec /usr/portage/eclass/" gives numerous
deprecation warnings; just games.eclass is not among them.
Please provide some guidance how (community-)developers are supposed to
handle games (in particular wrt games.eclass) in the future. This also
includes usage of /usr/games/{bin/lib/share} etc.
Regards,
tomboy64
next reply other threads:[~2016-02-07 10:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-07 10:38 M.B. [this message]
2016-02-07 10:43 ` [gentoo-dev] games.eclass policy Patrice Clement
2016-02-07 11:09 ` Michał Górny
2016-02-07 12:13 ` Daniel Campbell
2016-02-08 21:49 ` Michał Górny
2016-02-17 2:09 ` Daniel Campbell
2016-02-17 7:39 ` Michał Górny
2016-02-17 7:52 ` Michael Sterrett
2016-02-17 10:42 ` Michał Górny
2016-02-17 15:32 ` Denis Dupeyron
2016-02-17 16:22 ` Michał Górny
2016-02-17 17:19 ` Denis Dupeyron
2016-02-17 17:33 ` Michał Górny
2016-02-17 18:08 ` Denis Dupeyron
2016-02-17 18:38 ` Michał Górny
2016-02-18 1:06 ` Denis Dupeyron
2016-02-18 7:08 ` Michał Górny
2016-02-20 1:25 ` [gentoo-dev] " Ryan Hill
2016-02-20 17:13 ` Andreas K. Hüttel
2016-02-22 13:20 ` Alexander Berntsen
2016-02-23 16:42 ` [gentoo-dev] " Vadim A. Misbakh-Soloviov
2016-02-10 2:49 ` Ian Delaney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160207113827.314d5bf0@hatshepsut \
--to=tomboy64@sina.cn \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox