From: Alexandre Rostovtsev <tetromino@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: qa@gentoo.org
Subject: Re: [gentoo-dev] QA bikeshed: killing USE=dedicated in favor of uniform USE=client+server
Date: Thu, 20 Aug 2015 21:36:52 -0400 [thread overview]
Message-ID: <1440121012.4830.16.camel@gentoo.org> (raw)
In-Reply-To: <20150820194244.622b8f86.mgorny@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 858 bytes --]
On Thu, 2015-08-20 at 19:42 +0200, Michał Górny wrote:
> Hi,
>
> Right now, a number of game packages are using USE=dedicated to control
> 'installing a dedicated game server only'. Aside to that, some game
> packages also have USE=server that controls building the server itself.
> Non-game package use USE=client and USE=server.
>
> In order to improve uniformity of USE flags across different packages,
> the QA team would like to deprecate USE=dedicated and use USE=client
> and USE=server as appropriate.
>
> The problems I see with USE=dedicated are:
>
> - it is game-specific. The term 'dedicated server' is not used amongst
> other server/client model packages.
Please leave the flag as is - for those users who will be using those
ebuilds to install and run dedicated game servers, it's standard and
expected terminology.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 951 bytes --]
next prev parent reply other threads:[~2015-08-21 1:37 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-20 17:42 [gentoo-dev] QA bikeshed: killing USE=dedicated in favor of uniform USE=client+server Michał Górny
2015-08-20 18:03 ` hasufell
2015-08-20 19:32 ` James Le Cuirot
2015-08-20 20:17 ` hasufell
2015-08-20 19:56 ` Rich Freeman
2015-08-21 6:39 ` [gentoo-dev] " Duncan
2015-08-21 14:29 ` [gentoo-dev] " Ciaran McCreesh
2015-08-20 20:31 ` Alexander Berntsen
2015-08-20 21:19 ` [gentoo-dev] " Martin Vaeth
2015-08-20 21:33 ` hasufell
2015-08-20 22:06 ` [gentoo-dev] " Jason A. Donenfeld
2015-08-20 22:18 ` hasufell
2015-08-21 1:03 ` Rich Freeman
2015-08-21 3:11 ` Kent Fredric
2015-08-21 6:50 ` [gentoo-dev] games.eclass (was: Re: QA bikeshed: killing USE=dedicated in favor of uniform USE=client+server) Ulrich Mueller
2015-08-21 15:10 ` [gentoo-dev] games.eclass hasufell
2015-08-21 17:39 ` Rich Freeman
2015-08-21 18:17 ` hasufell
2015-08-21 18:44 ` Rich Freeman
2015-08-21 19:42 ` Daniel Campbell (zlg)
2015-08-21 21:09 ` James Le Cuirot
2015-08-22 7:33 ` Daniel Campbell (zlg)
2015-08-22 9:56 ` Rich Freeman
2015-08-22 11:10 ` hasufell
2015-08-22 14:32 ` James Le Cuirot
2015-08-22 15:25 ` Rich Freeman
2015-08-22 20:47 ` hasufell
2015-08-22 23:48 ` Rich Freeman
2015-08-22 18:01 ` Daniel Campbell (zlg)
2015-08-22 21:16 ` hasufell
2015-08-21 1:36 ` Alexandre Rostovtsev [this message]
2015-08-21 7:16 ` [gentoo-dev] QA bikeshed: killing USE=dedicated in favor of uniform USE=client+server Sergey Popov
2015-08-21 8:11 ` Kent Fredric
2015-08-21 10:58 ` Rich Freeman
2015-08-21 11:28 ` Alexander Berntsen
2015-08-21 12:04 ` Rich Freeman
2015-08-21 15:27 ` hasufell
2015-08-21 17:17 ` Rich Freeman
2015-08-21 18:29 ` [gentoo-dev] " Duncan
2015-08-21 8:31 ` [gentoo-dev] " Daniel Campbell (zlg)
2015-08-21 10:31 ` Rich Freeman
2015-08-21 11:01 ` Rich Freeman
2015-08-21 19:31 ` Daniel Campbell (zlg)
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=1440121012.4830.16.camel@gentoo.org \
--to=tetromino@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=qa@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