HP has made a lot of crappy packages. And they still are. Red Hat might do us all a favor if they send them a copy of the "Red Hat RPM Guide". In a meeting with HP in March, I expressed this to the VP of Linux Engineering. What I've had to do is re-roll a lot of HP packages.. In my spec file I dissassemble the rpm using rpm2cpio and take the crap out of %post %pre that I don't want and put it back together. Seth is right, don't encourage them. Make a working package and email it back to them and tell them "this is how it should be done." The worst package I've ever seen was from Netvault-- Their rpm of their backup software basically dropped some files in /tmp and then there was %post script that ran the installer. Ugh, what a complete mess and waste. James S. Martin, RHCE Contractor Administrative Office of the United States Courts Washington, DC (202) 502-2394 kickstart-list-bounces@xxxxxxxxxx wrote on 05/31/2005 05:59:02 PM: > On Tue, 2005-05-31 at 17:55 -0400, Matthew Miller wrote: > > On Tue, May 31, 2005 at 03:46:10PM -0400, Brian Long wrote: > > > written RPMs, this works great. However, I've come across the lovely HP > > > Insight Manager RPMS (hpasm, hprsm, etc) which seem to run "service > > > hpasm start" during the RPM postinstall (yuck). This wouldn't be too > > [...] > > > Any ideas would be appreciated. Thanks. > > > > I know there's the "tsflags=noscripts" option in the config file -- is there > > a way to do that from the command line? Then, you could add any other bits > > of the %post script to your kickstart file. > > > > Don't encourage them. > > It does not make sense to add this to the cli in yum in order to work > around a broken package. > > -sv > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/kickstart-list
