[CentOS] package conflict with libmodplug in rpmforge and in rpmforge and epel

[m.roth at 5-cent.us]

centos at kcburns.com wrote:
> On 04/16/2014 05:33 PM, m.roth at 5-cent.us wrote:
>> And no, do *NOT* use epel and repoforge - they very frequently have
>> conflicts, due to prerequisites of packaging.
>
> Does the use of yum priorities take care of this concern?

No. The problem is the way the packages are built into .rpms. I've seen
yum give up on stuff in the standard repos, because the manpages from a
i386 package conflicted with the manpages from a package, sometimes the
*same* package... but that was the x86_64 version. The rules for the rpm
install can specify (or not) whether to allow for this... but both epel
and rpmfusion have packages compatible with the base, and seem to do
pretty well with each other, while rpmforge doesn't consider them.

The upshot is that a package will want, for example, a specific library
that you *have*... but it was installed in package x.y.6, while the one
from repoforge is expecting it to have come from *their* package q.j.6.
The result is that it fails to install.

Is that any clearer?

          mark