public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Daniel Campbell (zlg)" <zlg@gentoo.org>
To: 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 12:31:53 -0700	[thread overview]
Message-ID: <55D77CA9.9020901@gentoo.org> (raw)
In-Reply-To: <CAGfcS_maYtR-OGZsiyz7=VFN40qF+5BpxrpkoA2-oOPJtQo=JQ@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 08/21/2015 03:31 AM, Rich Freeman wrote:
> On Fri, Aug 21, 2015 at 4:31 AM, Daniel Campbell (zlg)
> <zlg@gentoo.org> wrote:
>> Based on what I'm seeing in this thread, the problem seems to
>> center around the description and application of the `dedicated`
>> flag. I'm fully in favor of the `server` and `client` flags
>> because they're clear and consistent.
> 
> ++
> 
>> *However*, it was mentioned elsewhere in the thread that some
>> games don't allow a client and a server at the same time.
> 
> Can we actually get an example of one before we go making policy
> based on what seems like a really strange case (one which I'm
> skeptical actually exists)?

I'm not aware of such use-case, as it was mentioned by someone else.
It's a theoretical possibility, though, and games aren't always known
for having sane build systems or programming practices, so I think
it's worth considering.

> 
> It seems that in these cases either REQUIRED_USE gets used, but 
> preferentially the build system should be fixed or the package
> should be split.

Agreed.
> 
>> With the games.eclass deprecated, I don't really have a "good
>> practice" guide for making gaming ebuilds.
> 
> Just make them like any other ebuild.  The main thing games.eclass
> did was force users to be in the games group to run games, and
> install them in a special location.
> 
> The eclass isn't officially deprecated, but it probably should be. 
> You should install a game just like you'd install a word-processor
> or a web browser.  It is just another desktop application (99% of
> the time).
> 

Thanks, I'll keep that in mind when I get around to writing those
ebuilds. I'll also consult the games team before committing.

- -- 
Daniel Campbell - Gentoo Developer
OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net
fpr: AE03 9064 AE00 053C 270C  1DE4 6F7A 9091 1EA0 55D6
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJV13ylAAoJEAEkDpRQOeFwWgsQAKYTlKXP1bgyN68cDbVddnfE
kgggdVy3R2Zv0AHRfqbip4prrbbDv5+M0qifQ8RGa9WxQ4Fu5kVxUrFsJ1l2xO7O
VNSYDeBl4NVC+AqePDSsqzKCWojYR8hMbEhBvsC3hsxGeD28dBJ5P3yhQMHORvSy
T2K45wj/lXlJDKTrnI/3cwpWSNJM6u209pXLlU6XydsXt0lh9C+3pV2NGNuXuucw
jSkA2cGxRCGQqaGxWcVjXyPr2tRkWsFYr1kxyNqaJ7Meb9kX5QUFzkwBZAWR6Eq4
HV7kiM8CLujDJapbN2NwpsBs6Bo5e4jlJwmw8+kOLeMVXBbZFzf5q/vy3+vB9hds
ibGEc90tdEb+zo6lHMD8EhI7OlR5ckJ4yuLykzYqanB5bLzBXA9OKe/IgUtgrtVT
RadKh0v42Qo6Rck1uzCus0ZiTME1cykvvyrz+wQIvl1PHrdArwtqPNSIOtVGnngt
W2cjJUVs8bE2JA/ftHjrj7cLrsSicvJ9aRKCZLNMFHJIs7Wq923wQTCVZ/8/mhsf
Z2eX74plPuwk6H/8EmJPNTW2JmA5R2t759chJcaSfEW/Tgc0w1nsoMUCWnwxjF5E
x2Qxx5P7I0kEVqYXCJ2Z14NtRafO+Oq31t9OcxGuRYv/r/dK17w70uA652jr8FmX
arJW7R1aiYqch1p6FKhM
=Y7o9
-----END PGP SIGNATURE-----


      parent reply	other threads:[~2015-08-21 19:32 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
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) [this message]

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=55D77CA9.9020901@gentoo.org \
    --to=zlg@gentoo.org \
    --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