From: Kent Fredric <kentfredric@gmail.com>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] QA bikeshed: killing USE=dedicated in favor of uniform USE=client+server
Date: Fri, 21 Aug 2015 20:11:02 +1200 [thread overview]
Message-ID: <CAATnKFCEvvZ4iDznNj4jZCspGS9tovzYHvm8JbxZ4g+LvtSWzw@mail.gmail.com> (raw)
In-Reply-To: <55D6D038.2090702@gentoo.org>
On 21 August 2015 at 19:16, Sergey Popov <pinkbyte@gentoo.org> wrote:
> Now, THAT should be fixed either way - by moving 'dedicated' to
> 'server'(for those packages), or, preferabbly - by allowing
> USE='dedicated' to work as hasufell said - build ONLY dedicated server
> and no client at all.
Another compromise that *could* work if the installation is so
structured: Split the server behaviour into its own package.
games-whatever/foo + IUSE="server"
games-whatever/foo-server
That completely eliminates the required_use confusion. "foo" is always
providing a client, and USE="server" is just a convenience that few
will want.
If you want a server, install "foo-server".
Granted this is of course not always possible if the server and client
share files, but such a solution would be high on my considerations
were it me.
--
Kent
KENTNL - https://metacpan.org/author/KENTNL
next prev parent reply other threads:[~2015-08-21 8:11 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 ` [gentoo-dev] QA bikeshed: killing USE=dedicated in favor of uniform USE=client+server Alexandre Rostovtsev
2015-08-21 7:16 ` Sergey Popov
2015-08-21 8:11 ` Kent Fredric [this message]
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=CAATnKFCEvvZ4iDznNj4jZCspGS9tovzYHvm8JbxZ4g+LvtSWzw@mail.gmail.com \
--to=kentfredric@gmail.com \
--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