oops, I misspoke a little. What I do to get the same effect as --force is to supersede the file I want to overwrite in a custom rpm %post section that installs after the redhat rpm. In other words, I use rpm B to stomp a file owned by rpm A. Ugly, but effective. That means the original redhat rpm will fail a "rpm --verify" check, but that's not a problem in my case, as I can control the prerequisites for the things I need to mess with so that the reverse order installation can't happen. (consider if package A owns 'foo', and package B supersedes it afterward in a %post script. how do you install an upgrade to package 'A' without negating your change ?) Alternately you could I suppose roll your own modified 'not-from-redhat' variant to update the file in the rpm, but that's a bit of a pain to maintain. -- ---------- Vince.Skahan@xxxxxxxxxx --------- Connexion by Boeing - Cabin Network -----Original Message----- From: Tom Diehl [mailto:tdiehl@xxxxxxxxxxxx] Sent: Wednesday, April 23, 2003 8:41 PM To: kickstart-list@xxxxxxxxxx Subject: RE: [Yum] deploying and maintaining linux networks howto 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. I was not aware that one could force things in the %post.
