A number of years ago, I used Kickstart for this. IIRC, I used Perl to control the process.

Hope that is helpful....

Update:

ReiVo brings up a good point in Re^2: RPM Download Request. My experience with Kickstart was in a controlled environment where we had to maintain numerous identical workstations. The company I worked for had an agreement with RedHat(some version of enterprise support I seem to recall). Kickstart was our way of managing the identical state of machines. It was not unattended. I agree that un-attended updates are a bad idea. However, having a repeatable process across multiple machines does not imply un-attended. Just automated. Big difference. To minimize issues like internet connectivity during upgrades, we downloaded the ISO images and mounted them prior to selecting distribution to the LAN connected workstations. And prior to that, we updated the config for kickstart to ensure we got what we wanted. We deployed to a test workstation first, checked for functionality etc... , then if all was well (and it always was), we deployed during lunch breaks on off-shifts to minimize engineering downtime.

The point is that there are tools to do the job, and appropriately applied, they work well. Kickstart is just one I happen to recall working well with RPM based installs and updates/upgrades. Thanks RieVo for bringing that up.

...the majority is always wrong, and always the last to know about it...

Insanity: Doing the same thing over and over again and expecting different results...

A solution is nothing more than a clearly stated problem...otherwise, the problem is not a problem, it is a facct

wjw

In reply to Re: RPM Download Request by wjw
in thread RPM Download Request by carlriz

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.