Adding RPM's "at the end" of an install?

Say you have an installer program for a bunch of RPM's.

You want to add some 3rd party RPM's to the collection
of RPM's with which this installer has been tested.

But some of these 3rd party RPM's aren't very careful
with their Requires dependencies, so if you toss those
RPM's into the collection, a high percentage of them
fail to install.

Is there some way of constructing a special RPM that
should always be installed at the end of the tested
RPM's, and change minimally your 3rd party RPM's to
depend on that single RPM? That is, without having
a huge list of Requires in that special RPM?

Yes, it'd be cleaner to go fix all the dependencies
in those 3rd party RPM's, but that should be fixed
upstream... We may be able to file bug reports
with each vendor about their broken dependencies,
but 1) some may not care and 2) I doubt many of them
would be able to respond "soon enough" for our need

Thanks!

Dan Stromberg - Datallegro <dstromberg.RemoveThis@datallegro.com> wrote:
>
> Is there some way of constructing a special RPM that
> should always be installed at the end of the tested
> RPM's, and change minimally your 3rd party RPM's to
> depend on that single RPM?

Not really. Either you can rebuild all packages in question, and then
you can make sure that all "Requires" are in order, or there are some
reasons why this is not possible and then you cannot "change minimally"
what you already have.

Keep in mind that the fact that you do not have sources does not
prevent you from redoing packages. You %build section in specs
you write can be "no-op". But that could be some external factors,
like legal, which make that impossible.

> That is, without having
> a huge list of Requires in that special RPM?

You can always put together a "master" package which does not install
any files but has on "Requires" list all other packages you have in mind
and their dependencies. Installing that one will have an effect of
"pulling in" everything else needed here if you are using an installer,
like yum, which checks dependencies.

Something of that sort is done, for example, in a package
'xorg-x11-drivers' from Fedora 6 and 7 distributions so you
have a spec you can use as a pattern.

Michal