seth vidal wrote: >>Long answer is : You *CAN* make your own repository if you have enough >>machines to patch to make it worthwhile, or you have machines that can't >>talk to the internet. You'll need to download all the available errata >>using a machine that *can* get to RHN, stick 'em in a web-served >>directory, and yum-arch over it. (Or create-repo if you've mashed your >>RPM/Python libs to work with the latest YUM.) >> > > > rebuilding yum 2.1.x on rhel3 makes it work w/o any new libs or changes. > > Just rebuild the source rpm. > > I was fairly careful to make sure that worked. :) I'm using yum 2.0.7 (IIRC) on RH ES 3.0, for reasons Steve explained. I'll check the Changelog and test out 2.1.x if thers's time. http://dag.wieers.com/ has a yum rpm available. Works like a charm once you setup your own repositories. The only small "downside", you have to remove older kernel once in a while, /boot gets a little messy after a dozen of kernel updates, especially if it's a smp/ht box, which doubles the amount of kernel. Anyway, many thx to all people involved making yum possible, I can hardly image how many hours of work yum has saved me.;) If one of you is over here (Germany), just drop me a mail, I'd be happy to invite you on a few cups of German beer.;) The OP could upgrade to CentOS, simply using yum. Thx and keep the great work! Michael Heiming
