On Fri, 2007-05-04 at 22:02 +0200, Daniel de Kok wrote:
On Fri, 2007-05-04 at 22:52 +0300, Panu Matilainen wrote:
On Sun, 29 Apr 2007, Johnny Hughes wrote:
We are working out the last remaining technical issue with yum-2.4 on CentOS-3 (that we have found thus far), which is that yum-2.0 (and up2date in C3) sets newly installed kernels to be the default. In EL4, that is handled by the OS script "/sbin/new-kernel-pkg" (provided by mkinitrd), however in EL3 that functionality was done instead by up2date / yum. We won't modify how mkinitrd works on CentOS-3 (that is a very important core package and we don't change that kind of functionality from upstream), thus the only ohter option is to modify yum to do it.
That should be doable from a plugin, without touching yum itself.
This was initially implemented as a plugin. But we decided to integrate this into yum, following the principle of least surprise. E.g. on machines with a modified yum configuration (where plugins are not enabled), a plugin would modify behavior from what it was previously.
Right ... doing it as a plugin is a great idea, and if we were adding it as optional functionality where it did not exist already that would be the method we chose.
But in this case, it is already built into the version 2.0.8 yum that this will replace in CentOS-3. So this is providing functionality that already exists in the current yum to the newer yum. I don't think I want to roll in the "requirement" to also enable and properly configure "plugins" to get normal out of the box behavior of the older version in the newer one.
The new patch is only applied into yum-2.4.x IF it is compiled on a system with python-2.2 (el3) ... if compiled on python >= 2.3 (el4) then it is not applied.
The process will be to upgrade/install the new yum (plus requirements) as a separate install out of CentOSPlus for C3 ... then adjust your yum.conf to use /etc/yum.repo.d/, then use the new yum.
Thanks, Johnny Hughes