On Fri, Aug 19, 2011 at 3:17 PM, James Antill <[email protected]> wrote: > On Fri, 2011-08-19 at 00:21 +0300, Ville Skyttä wrote: >> On 08/18/2011 07:09 PM, James Antill wrote: >> > The idea is that sometimes you want to say "make sure the entire >> > dep. tree for package XYZ is at the latest version" >> > >> > Things this patch doesn't do: >> > >> > 1. local packages. >> > >> > 2. implied deps. ... like @buildsys / @core. >> > >> > 3. recursive updates for updates that add new deps. >> >> 4. update the yum.8 man page ;) > > Yeh, I always do those in a separate patch because they more often hit > conflicts when backporting. FWIW: > > +.IP "\fBupgrade-all\fP" > +This command works like a simple version of "\fBupgrade\fP" however all the > +depedencies for the package specified are also checked for upgrades. Thus. > +"upgrade-all yum" will check for updates on many packages, including glibc. > +.IP > > _______________________________________________ > Yum-devel mailing list > [email protected] > http://lists.baseurl.org/mailman/listinfo/yum-devel >
Ack to the code & fuctionality, but I don't like the name of the command 'update-all' it sounds like what 'yum update' does, update all packages. what about: update-deps The ideal would to have it as a option to the yum update command. yum update yum --some-option-name --some-option-name could be --resolve (as in yumdownloader) --update-deps --with-dependencies but this will need some kind of drastic changes to how yum handle option, if we want to introduce command specific options (can be done with argparse) The name is not a blocker for me, but when it add, it is hard to change. Tim _______________________________________________ Yum-devel mailing list [email protected] http://lists.baseurl.org/mailman/listinfo/yum-devel
