On Tue, Jul 6, 2010 at 4:12 AM, Karanbir Singh mail-lists@karan.org wrote:
Thats where this whole thing started from. The problem is that the yum-security plugin needs some specific info available in the CentOS repo's and the place where its generated has licensing issues with us just using it as is.
So the thinking is that if there is a generic backend info pool of all this information, changelog, package payload, package headers, metadata around the packages, their relationships with each other and then amalgamate that into an ( hopefully ) easy to use backend, we can then write multiple frontends - each with its own utility.
Ideally I'd like to just work on the backend and release a generic api around it using rest/json for everyone to scratch their own itch :)
Spent a few hours working on this over the weekend and feeling quite confident that there should be something usable soon.
Hi Karan, Any good news yet? ^^