On Mon, 3 Nov 2008, Toshio Kuratomi wrote:
Seth Vidal wrote:
A couple of simple ideas:
tagging a-la flickr. If we key it on pkg name, we can keep the metadata
from changing a lot. We could do a pre-made sqlite db, for example, and
keep querying simple.
But let's say an average of 5 tags per pkg name at 7000 pkgs ends up
being 35000 tags. Searching shouldn't be ridiculously hard and having a
table that maps the other way tag->pkg shouldn't be too bad, either.
Toshio, any thoughts on if that's enough info?
That should be enough to create the UI I was thinking of.
My main question would be, do we want this to be wholly separate from
comps or to integrate somehow? If it's separate then we can implement
this and the feature is ready to go. If it's integrated then Nicolas
Mailhot's questions become important to answer.
I think we do POC on its own and then figure out if:
1. it should be merged into comps
or
2. comps should be merged to it
or
3. if all group selection should be redone to match up with a tag-based
pseudo-hierarchy.
-sv
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
