On Mon, 2009-02-02 at 23:10 +0100, Maciej Mrozowski wrote:
> On Monday 02 of February 2009 22:15:53 Luca Barbato wrote:
> > not sure how useful could be but could make more sense even if right now
> > kde-base contains everything comes from the main kde distribution.
> To be more specific, kde-base contains everything (and only) that is
> distributed as KDE stable release (no extragear included). And it causes
> confusion as when packages are dropped from KDE release schedule (so they
> usually go back to extragear to release when they want), one needs to look to
> new place for them (in kde-misc or somewhere else).
> Actually categories are bad idea imho.
> I was thinking, maybe it would be possible to drop categories completely in
> the future (maybe keeping symlinks for compatibility and to ease migration)
> and to put *all* packages in one directory - that would require making all
> names unique of course.
> "Categorization" could be provided for user/search tools as tag clouds being
> defined in metadata.xml as vector of tag:weight values where tag would be some
> word from defined dictionary (word like "mail" "client" "kde" "dns" or sth)
> and weight - real value [0,1] defining how relevant is that tag.
> For compatibility's sake symlinks could be provided, in.ex. sys-devel/gcc ->
> But that's just an off-topic.
I agree that a tag kind of approach would be nice. Someone should
actually do work on it.
Here's a random similar idea that I think might work well as a GLEP
proposition, that I was about to reply to a different subthread before
noticing this post:
Packages metadata.xml can be extended with an unlimited amount of <tag>
elements, whose #text can be a tag string, but one that is limited to a
given list in some other place - to have a list of existing tags and not
just randomly have tags for everything. Make an effort to populate all
packages with sensible tags. Then write tools around it that can show
you all packages with a given tag or tags, what tags exist, etc. Those
will be your new categories that answer the question of "what mail
clients are there" (mail-client tag) or "what mail clients are there
using GTK+, well suited for a GNOME environment" (mail-client and gnome
Keep categories in place for repository tree sanity (not a huge amount
of directories with all packages being sibling dirs) and easier
implementation of it all. No-one really types in the categories anyway,
and with a tool that deals with the tags, you don't look at the subdirs
either - so categories for the user just become a way to differentiate
packages with the same name for the few cases there are equal names.
However those that prefer the categories approach, can keep using it.
Developers also deal with categories, but that's easy enough to keep
going as is.
Less radical, less controversial, better viability to actually get done.