On Thu, 2005-09-29 at 13:16 -0400, Jack Neely wrote:
> > okay but HOW can it know? You've described what you see
as problem but
> > you haven't described any way yum can know about what's you think
> > _should_ be going on.
>
> But it is a problem and we should (read: need to) solve it imho. How?
> I'm not sure. We could
>
> - package modules for all kernels in one package (I don't really like
> this idea, but if this is the only solution we need to go it imho)
> - fix our proposal so it works better with yum (hint's from you are
> greatly appreciated)
> - add support for yum somehow so it can resolve the dep correctly. I
> unfortunately don't know neither yum nor python enough to fix that
> myself :-|
>
All kernel-modules packages require the exact kernel they are built
against. Yum does/will use this information to figure out which one of
the kernel-module packages are the best for your system.
However, I need to figure out and change some of the more un-fun code in
Yum to support this. Its not as easy as it sounds.
what things need to be changed or are you talking about mostly code in
your patch?
-sv