On 11 Nov 2003, seth vidal wrote: > I think the idea is fine but this, like a lot of other things need to be > added outside of yum, not in the core program. Otherwise the yum command > ends up being yum [command] packages > > where command is one of 80 different options. > > I don't think that is good design and can you imagine that if statement? > ;) > > > I think the goals I need to work toward are a yum library that does the > following and ONLY the following: > > - builds and parses the metadata classes into the repo lists > - resolves dependencies > - handy rpm-ish functions > - builds pkg info for installed pkgs > - exception class > > - separately a system for parsing the yum config file. And has an incredibly sane internal set of data structures and an extensible and well-documented ABI. As you say, this could be done now "outside of yum" with an e.g. perl script that does some obvious things, but they would still be inefficient -- running yum's core a whole bunch of times instead of just once to build its internal installed/uninstalled lists with their attached/hashed metadata. > so then people writing other apps that could: > - slurp in the config file > - get the pkg lists > - output something or resolve deps on something. > > > I think this would cover a lot of the meta-yum ideas that people are > coming up with. I want this done for my own sanity too. > > It's just a matter of finding the time in my copious spare amounts. Sure. I may be able to help some with that if I don't take on any new tasks for a few months. rgb -- Robert G. Brown http://www.phy.duke.edu/~rgb/ Duke University Dept. of Physics, Box 90305 Durham, N.C. 27708-0305 Phone: 1-919-660-2567 Fax: 919-660-2525 email:rgb@xxxxxxxxxxxx
