>I don't see it solving that either. Nobody *likes* those >kernel-module-foo-2.6.10-1.741_FC3 type names but nobody has come up with >a solution which covers all the cases without the kernel version in >package name. Oh and I think special name-based hacks are required for >this anyway... and I seriously doubt you want those in yum proper. > >If I understood correctly the Xtrigger-stuff should allow pushing the >special kernel-module handling to a separate script/module and enabled >only where needed, somewhat like my apt lua-script which handles (or >at least tries to :) this mess. We could spawn things out of xtrigger -however xtrigger will play hell with a gui front end for output reasons. thoughts? -sv
