I find myself responsible for managing an ecosystem of rpms for our
custom application. One of the interesting sticking points is what we
call the "db" rpm. Most of the other rpms won't run correctly unless
that rpm is installed. The catch is, it's got to be installed on the
database node(s) of the application, not the application nodes that
the other rpms are being installed on.
I haven't seen anything to indicate that the rpm format can handle
such a dependency. Have I overlooked something? Anybody got *any*
ideas on how such a thing might be handled?
Thanks,
<mike
--
Mike Meyer <mwm@xxxxxxxxx> http://www.mired.org/consulting.html
Independent Network/Unix/Perforce consultant, email for more information.
O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list
