On Wed, 2003-04-23 at 23:40, Tom Diehl wrote: > On Wed, 23 Apr 2003, Skahan, Vince wrote: > > > > > I solve it a different way, do the forcing in %post and set my dependencies so it installs after the RedHat supplied one that thinks it owns the files. > > > > The only example I can think of offline here is putting a custom banner in /etc/issue, which is (I think) marked config/noreplace, which is of course a bug. > > Sangoma Wanrouter cards also have this problem. The driver comes with the kernel > but Sangoma occasionally releases updated drivers. So far the only options > I have found are either install the new driver from a tarball (not good) or > install the rpm with --force (even worse IMHO). I love their hardware and > drivers but their rpm is a problem. I was not aware that one could force > things in the %post. If this is right I will need to look into this. > I would really prefer not to have to rebuild a kernel rpm just to update a > module. Too much like work for me. can you build the module as a different name and just deploy it alongside the kernel? you'd have to rebuild it with each kernel update but <shrug> that's not very hard. -sv
