On Thu, 2005-09-08 at 07:11, Johnny Hughes wrote:
> >
> > If you managed a set of servers running homegrown code that
> > may or may not be sensitive to library and utility program
> > versions, what steps would you use to keep a test server
> > up to date, then after performing any needed application
> > testing, to roll out the same changes to the production
> > servers in various different locations? The object is to
> > install exactly the updates you just tested in spite of any
> > subsequent repository changes or out-of-sync mirrors.
> >
> You would run a local mirror that only had the updates you tested on
> it :)
Local to what? The production boxes are distributed but have good
internet connectivity. The test box only has so-so internet
connectivity. Isn't having to do that an admission that yum
doesn't really do a good job of managing the packages you
want on a box?
Actually I think some invocation of rpm -q will give a list
of installed packages that you can feed to yum to install on
another machine, but it is not at all intuitive. Don't the
people writing package management tools actually manage any
machines or understand that keeping them identical is
desirable?
--
Les Mikesell
lesmikesell at gmail.com