Package updating

[Horst von Brand]

seth vidal <skvidal at linux.duke.edu> wrote:
> > But this (as the scripts on the page) f.ex. today upgraded cpp (which pulls
> > in a lot of gcc-related stuff), and then tries to upgrade those too, one by
> > one.  Ideally, after installing something it should cut down the list of
> > stuff to install, and if something can't be upgraded don't try the stuff
> > depending on it.

> so if there is a cascade of dependencies (a deps b deps c deps d deps e
> deps f) you're going to pull in most of the packages anyway.

Yes, I know. But the setup time is non-trivial (and adds up for a couple
dozen packages), plus the annoyance of getting one version of the repo data
and then another...

> What if I told you there was the information in yum's transaction set
> about those dependencies and that after the initial transaction set was
> determined you could, if you wanted, break the transaction set up based
> on those deps into discrete groups of transactions to run?

I know. But I'm no Python expert, so I'll pass (for now at least).
-- 
Dr. Horst H. von Brand                   User #22616 counter.li.org
Departamento de Informatica                     Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria              +56 32 654239
Casilla 110-V, Valparaiso, Chile                Fax:  +56 32 797513