On 9/7/05, Les Mikesell <lesmikesell@xxxxxxxxx> wrote:
> On Wed, 2005-09-07 at 11:53, Greg Knaddison wrote:
>
> > That is true, but in yum2.4 (soon to be available for CentOS4, or you
> > can build/install it yourself) this is greatly improved. Also, yum
> > 2.4 includes the "shell" where yum reads in the information, gets
> > itself ready, and then you can ask it to do a whole bunch of stuff
> > without having to ask for it all in advance on the command line. It's
> > pretty neat.
>
> It's always painful when utilities add the 'pretty neat' stuff
> _after_ the scripts that use them have been written.
I'm not sure what you mean here.
> Is there
> a way to tell yum that you don't care about anything that
> changed since the last time you ran it (a few seconds ago) and
> it doesn't have to do all that work again?
No.
> Or better yet,
> a way to tell it that you don't _want_ it to consider anything
> that changed since you did an update on a different machine
> and you want it now to apply exactly the same changes on
> an important machine that you tested elsewhere (preferably
> pulling from exactly the same repository mirror or using some
> transaction checkpoint to ensure an identical operation).
As long as you use specific instructions to yum like "yum install
foo.1-3.386" and you have a clean and simple set of conf/repos files,
then yum will do a very specific thing. If you have multiple
repositories in your configuration and you just say "yum update" then
it might not behave exactly as you desire.
Greg
