> Ditto wrto smartpm. /me looks at the smartpm code. it doesn't seem like it's using the rpm depsolver overly much. It's using it for the transaction - but it's solving the deps all by itself. > rpmlib (and everything that uses) is quite stupid about choosing between > multiple provides, for one obvious example. Multilib, and kernel's, are > other known deficiencies in rp[mlib mechanism (or, if you will, the > lack of better policy mechanisms for depsolvers). yep - which is why I'm looking forward to using the new check objects that paul was talking about - to better identify the requiring package. -sv
