>> On a somewhat related note (to my previous question), is there a >> simple procedure documented someplace for rebuilding the comps.rpm >> file with the new package information? Seems like this should be >> part of my package update process... >> > I've still to figure out what value this RPM actually offers. What is its > history, and what is it supposed to do? I guess I may be speaking of the rpmdb package -- it's the database RPM uses when offering "suggestions" to resolve deps. Clearly it's not an important issue, but I thought it'd still be worth solving... -Matt-