| 1 |
On Wed, Jun 22, 2011 at 14:19, Ciaran McCreesh |
| 2 |
<ciaran.mccreesh@××××××××××.com> wrote: |
| 3 |
> On Wed, 22 Jun 2011 21:55:18 +1200 |
| 4 |
> Kent Fredric <kentfredric@×××××.com> wrote: |
| 5 |
>> I'd love a tag solution, that'd be nice, is there a GLEP for it yet? |
| 6 |
>> And if so, how long will it take to get this "tag" feature supported |
| 7 |
>> by EAPI standards? |
| 8 |
> |
| 9 |
> The slow parts are coming up with a good design, getting the Council to |
| 10 |
> approve it, and getting Portage to implement it. The fast part is |
| 11 |
> getting the PMS bit done. |
| 12 |
> |
| 13 |
> The problem with tags is that all we've heard so far is "we should have |
| 14 |
> tags!", with no description of what tags are, what they'll solve or how |
| 15 |
> they're used. |
| 16 |
> |
| 17 |
> -- |
| 18 |
> Ciaran McCreesh |
| 19 |
> |
| 20 |
|
| 21 |
Tags are basically keywords you can use to describe packages, allowing |
| 22 |
you to easily search and explore your options based on what the |
| 23 |
packages actually does (if we want to get technical, anything that |
| 24 |
identifies a package is a sort of tag: name, version, license, set, |
| 25 |
checksum, etc.). It's just a vocabulary that eases the burden of |
| 26 |
human lookup. The categories we have now are essentially (pairs of) |
| 27 |
tags tied to a treelike structure in an actual filesystem, and I'd |
| 28 |
wager that's a decent place to start, too-- probably the most |
| 29 |
prominent problem I can see with the current method comes from these |
| 30 |
edge cases where one category is obviously not enough. The obvious |
| 31 |
solution is probably to just stick our semantic metadata into the |
| 32 |
metadata.xml. So for...say, media-video/kdenlive, |
| 33 |
<cat>media-video</cat>[1] becomes more like this: |
| 34 |
|
| 35 |
<cat> |
| 36 |
<tag>media</tag> |
| 37 |
<tag>video</tag> |
| 38 |
<tag>kde</tag> |
| 39 |
<tag>editors</tag> |
| 40 |
</cat> |
| 41 |
|
| 42 |
The canonical tag list needn't even expand beyond what we have already |
| 43 |
(for the time being; attempting to keep your vocabulary entirely |
| 44 |
static is a Bad Thing. Humans are amazing at finding new things that |
| 45 |
need tagging. Getting ahead of myself, though). |
| 46 |
|
| 47 |
In the practical sense, we can probably just whip out a quick script |
| 48 |
and get 98% coverage; package maintainers should be encouraged to add |
| 49 |
relevant tags to the packages under their care as needed. |
| 50 |
|
| 51 |
--Wyatt, hoping this text is plain as it says it is. Sorry if it's not. |
| 52 |
|
| 53 |
[1] Let's just assume for the sake of argument that kdenlive actually |
| 54 |
has a <cat> field in its metadata file. |
Archives