On Mon, 3 Nov 2008, Toshio Kuratomi wrote:
I think we should be storing tag information into the packagedb. But I think it should be used to generate static files that are used in other tools. I'm leaning towards the idea that there should be separate files for the installer and general use (so that the installer isn't sprinkled with thousands of libraries but one could still use yum to search for "all packages that have a 'python' 'library' to do 'ssl'").
We can add these to the items that yum already searches from a 'yum search' fairly easily.
Note that this requires quite a bit of work. The packagedb currently operates on SRPMS-only. It should be easy to add built packages to the data model but the whole infrastructure of populating that data, displaying it, etc will need to be built. If someone would like to work on it, I'd be very happy to help get you working with the codebase.
The only trick I can think of is how to store this info so it is: 1. compact 2. not constantly being re-downloaded. 3. not irrationally over-tagged so you get waaaay too many matches. -sv -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
