[Yum-devel] kernel-module plugin ...

[Matthew Miller]

On Tue, Jun 07, 2005 at 11:42:01PM +0300, Panu Matilainen wrote:
> Without the ugly uname-hackery the "easy" part stops the minute you try
> to do an update to a module where the kernel version itself doesn't
> change: you can't just do a regular update for those packages, you need
> to instead do a manual "locate and erase a single version of the kernel
> module package + install a new one." I haven't given the implementation
> too much thought but I have this funny feeling it's not easy to shoehorn
> into something sane enough to go into yum proper.
> But then, the uname-mess isn't "easy" on anybody either :)

Wait, why would that happen? Just name the module with its own name and its
own version, and it'll upgrade itself fine.

My current 'solution' is to just make sure we put an updated openafs kernel
module package in our repo before or at the same time as a kernel update.

And our openafs package contains modules for all kernels up to that point.
I'm not terribly happy with this in theory, but in practice, there have been
no problems at all. The problem, of course, comes in when the kernel and
modules are coming from different repositories.

Since that's not a problem here, and won't be if we get some kinda
buildsystem trigger in Extras by the time I feel like OpenAFS is ready to go
in there, I don't feel an urgent need to come up with a better hack -- I'm
willing to wait for something really elegant to appear.



-- 
Matthew Miller           mattdm at mattdm.org        <http://www.mattdm.org/>
Boston University Linux      ------>                <http://linux.bu.edu/>
Current office temperature: 80 degrees Fahrenheit.