Forgot your password?
Create an Account
You are viewing illiterat
(Ustr, micro string API)
(and-httpd - simple, fast and secure)
(String library comparison)
True, we are planning on exploring changing the model when we can store extra data in the rpmdb. I'm not 100% sure it will be a good idea, due to the corner cases (and what happens if/when group membership changes) ... but we'll certainly try it and see what it looks like.
We have also written code to store data directly in yum, but Fedora is against it as that would then force any other package managers to either repeat the data or talk to yum. The idea being if everyone could just talk to rpm that would be much better (and there would be only one real DB anyone needs to care about).
But if that change happens I still think it'll be better to present the user with "this group contains these pkgs, install some/all of them?" rather than just the "install group [X]" type option ... and also to remove core pkgs from weird groups.
The complete list of rpmdb pieces we want are roughly: 1) what repo. was X installed from 2) was it installed directly, via. a group or via. a dep. 3) what yum groups was it in. Other devel priorities are: