Gentoo Archives: gentoo-dev

From: hasufell <hasufell@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] RFC GLEP 1005: Package Tags
Date: Sun, 23 Mar 2014 13:03:13
Message-Id: 532EDB7C.9050607@gentoo.org
In Reply to: Re: [gentoo-dev] RFC GLEP 1005: Package Tags by Ciaran McCreesh
1 -----BEGIN PGP SIGNED MESSAGE-----
2 Hash: SHA512
3
4 Ciaran McCreesh:
5 > On Sun, 23 Mar 2014 00:04:08 +0000 hasufell <hasufell@g.o>
6 > wrote:
7 >> Ciaran McCreesh:
8 >>> On Sat, 22 Mar 2014 15:33:27 -0700 Alec Warner
9 >>> <antarus@g.o> wrote:
10 >>>> https://wiki.gentoo.org/wiki/Package_Tags
11 >>>
12 >>> And do what with them? Right now this is a solution without a
13 >>> problem.
14 >>>
15 >>
16 >> Finding packages. Descriptions are not consistent, categories
17 >> too generic.
18 >
19 > Please explain, with examples, how tags will help with this.
20 >
21
22 When thinking about games, it is pretty obvious and common practice on
23 almost any gaming platform/service like steam. You can't just say
24 "this game is an rpg"... it may be a mix of genres. Tags may even
25 identify features like "multiplay". USE flags cannot deliver that,
26 because there is no "multiplay" or "3rd-person" flag for obvious
27 reasons. Descriptions try to be short and and give an idea what the
28 game is about, not list all the possible genres or common search terms.
29
30 It also works the other way around. There are a lot of applications
31 that are scattered across multiple categories like terminal emulators
32 or file managers. The user ends up searching the web or wiki instead
33 of using portage tools which would be far more efficient.
34
35 so we have:
36 * tags to extend categories, e.g. when a package might fit in more
37 than one
38 * tags to group similar packages which are scattered across multiple
39 categories
40 * tags for features or attributes that cannot be expressed by USE
41 flags and cannot be guaranteed to be part of the description
42 * and so on
43 -----BEGIN PGP SIGNATURE-----
44
45 iQJ8BAEBCgBmBQJTLtt8XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
46 ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMDlCNDQ4NjEyNDI4NjA5REVEMDI3MzIy
47 MjBDRDFDNUJERUVEMDIwAAoJECIM0cW97tAgn3QP/0KLFi6Zdv/OkdwMi05gXqlr
48 NHnHAPf2v83gTeAikBaXRq+P11wWzraUPMrQBNe6agU2VmQGpJTt97KrVzzXJAuQ
49 ND1W2Dne6wV/c61UY/KDnGExb9QSXi6ow5eNZoJjoX1sUEorXaNDlI57sYaywlny
50 auT45Vhp87jwJLFydM4dGK4girbqSPR145bLumdB1fj5PGKc9z3e8MT2MQ+4UgYo
51 m4VGWxoJ//j6TX6Wv5zk0WJRPVoRdOqcTcficp90Km56d+eDV9Ijx5K0ZIQ46+7z
52 zj0xZvCLGKYsELgQlXHrCHrhYH12xkyo54WzVP2SpLN7AldKs73qr+Ntst3cLxUw
53 HL7inMHzRJoGsGbuYVXPzfOyDC23LDaofJrMjdny/vrUfA/I+Iu6NgAjAcy59QaC
54 QtW/DIpoZtosHSz6Bh4UG89a/KwhgVzPyJ2C/On0FtOv6oJmGjuCRj3SfH1hM5s8
55 6D3DYxXDFjfJR8WPrnTpwyMDaPgMP1Aow+WowEHFnp9ApBa8at1QONJm020SBZZx
56 f7vSi6Iu6C34kg6dzojuVQoSoP/wpzWDksh9hNRhrZnsefpjZRCN5cCjMqMI30ua
57 ZTU7vVG1BAeUjB18EzPIccLrk/2Tv8QDYvIRnNHsFWdedOQK7t5cbIo9tmIpYmNb
58 ucdX2RTAXEoxjN/dCgIV
59 =SPv7
60 -----END PGP SIGNATURE-----