> > 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. Jack -- Jack Neely <jjneely@xxxxxxxx> Campus Linux Services Project Lead PAMS Computer Operations at NC State University GPG Fingerprint: 1917 5AC1 E828 9337 7AA4 EA6B 213B 765F 3B6A 5B89 -- Fedora-packaging mailing list Fedora-packaging@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-packaging
