1 |
On 25 March 2014 03:55, Damien Levac <damien.levac@×××××.com> wrote: |
2 |
|
3 |
> A lot of people already replied to this question: package search. |
4 |
> |
5 |
> A trivial example, a user want to know all terminals available in portage. |
6 |
> Of course he could try a `emerge --searchdesc terminal`, but then he would |
7 |
> get anything mentioning terminal in the description: which would probably |
8 |
> include a lot of "terminal applications" which are not terminals |
9 |
> themselves... |
10 |
> |
11 |
> `emerge --search terminal` just doesn't cut it as "konsole" wouldn't be a |
12 |
> result but is a terminal emulator... |
13 |
> |
14 |
> On the other hand, terminals are spread through many categories |
15 |
> (gnome-terminal in gnome-base & konsole in kde-base to name the most |
16 |
> obvious example). |
17 |
> |
18 |
> Thus tags are a nice way for user to find the applications they want. |
19 |
> |
20 |
|
21 |
|
22 |
This example for me suggests we'll need to have some kind of process of |
23 |
defining what tags should be used for what things, similar to how we have a |
24 |
process for global USE, mostly, because inconsistency is a bad thing here. |
25 |
|
26 |
Because looking at this example and the results of `eix -cS terminal`, I |
27 |
see lots of things that may also be ambiguously tagged "terminal" due to |
28 |
being a terminal based application. |
29 |
|
30 |
Thus, either "terminal-emulator" or "terminal-app" or similar tags seem |
31 |
necessary. |
32 |
|
33 |
emerge --search tag:terminal-app tag:jabber-client ( or similar ) should |
34 |
thus result in net-im/mcabber |
35 |
|
36 |
And now that we're starting to flesh out mock tags that may make sense, it |
37 |
quickly seems we'll eventually want some kind of tag hierarchy. |
38 |
|
39 |
But as long as the tag is restricted to [A-Za-z-]+ or similar, we should |
40 |
have enough syntactical space to add a hierarchy in later if we find out we |
41 |
need it. |
42 |
|
43 |
For the sake of avoiding bikeshed, we should avoid hierarchy until we've |
44 |
proven tags are useful and have discovered we really need hierarchy. YAGNI |
45 |
|
46 |
-- |
47 |
Kent |