1 |
On Fri, Mar 28, 2014 at 4:39 PM, Kent Fredric <kentfredric@×××××.com> wrote: |
2 |
> |
3 |
> This example for me suggests we'll need to have some kind of process of |
4 |
> defining what tags should be used for what things, similar to how we have a |
5 |
> process for global USE, mostly, because inconsistency is a bad thing here. |
6 |
> |
7 |
Yes, you want a controlled, well-defined vocabulary. That's |
8 |
important. On the other hand, don't get too bent out of shape about |
9 |
it. These things fall over when you start adding dumb arbitrary |
10 |
restrictions like "there needs to be consensus" or "there need to be |
11 |
at least n packages beforehand". |
12 |
|
13 |
> Because looking at this example and the results of `eix -cS terminal`, I see |
14 |
> lots of things that may also be ambiguously tagged "terminal" due to being a |
15 |
> terminal based application. |
16 |
> |
17 |
> Thus, either "terminal-emulator" or "terminal-app" or similar tags seem |
18 |
> necessary. |
19 |
> |
20 |
terminal: terminal emulators. Make it an alias to terminal_emulator. |
21 |
cli: things that have a normal, line-based terminal interface. See also: curses. |
22 |
|
23 |
It's not hard to choose good, unambiguous tags when you can use |
24 |
aliasing to shorthand and unify. That's why it's more important than |
25 |
implication, because controlling your vocabulary is seriously |
26 |
important. |
27 |
|
28 |
> And now that we're starting to flesh out mock tags that may make sense, it |
29 |
> quickly seems we'll eventually want some kind of tag hierarchy. |
30 |
> |
31 |
No. You really, really, reaaaaaally don't. At least not in the sense |
32 |
that you seem to be thinking. It makes tags annoying to add and |
33 |
annoying to use, so no one does either and the whole thing falls over. |
34 |
|
35 |
> But as long as the tag is restricted to [A-Za-z-]+ or similar, we should |
36 |
> have enough syntactical space to add a hierarchy in later if we find out we |
37 |
> need it. |
38 |
> |
39 |
Don't worry, we won't. With only the facilities I've outlined in my |
40 |
first post, the system will scale well beyond a million packages and |
41 |
tens of thousands of unique tags, so don't worry too much about |
42 |
exhausting our semantic description space. |
43 |
|
44 |
Cheers, |
45 |
Wyatt |