Normally that is why you use rpm dependencies. You can install all of them as needed from a single call to rpm. If you need to adjust something once another package is installed use a trigger inside of the package. You can always build a meta package that has nothing but package dependencies that help you install the correct packages.
The answer to the above question is no but if things are packaged correctly why would you want to make is so hard. On Wed, Dec 3, 2014 at 6:11 PM, chris (fool) mccraw <[email protected]> wrote: > Last time I had to do something like that, I shipped a shell script with a > bunch of rpm's embedded in it (in a shell archive), which first extracted > them and then installed them serially (where needed) and in a group (where > not needed). > > This worked well enough to circumvent the problem. > > This was 2001. Sad to hear things haven't improved in that world, yet! > On Dec 3, 2014 5:56 PM, "Daniel Herrington" <[email protected]> wrote: > > > All, > > > > Can you have RPM call a third party installer that then calls RPM? > > I tried this a month ago and could not get around a lock error on the rpm > > db, I googled and saw an email thread form some years ago where the reply > > was no. I'm wondering if I just didn't look hard enough. I eventually > > abandoned for a self-extracting installer, but thought I'd revisit the > > problem > > > > thanks, > > > > -- > > Daniel B. Herrington > > _______________________________________________ > > PLUG mailing list > > [email protected] > > http://lists.pdxlinux.org/mailman/listinfo/plug > > > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
