On 17.03.2015 01:00 PM, Michael DePaulo wrote:
> It appears to be due to line 31 in x2gomatebindings.spec:
> Requires:       gtk2 or gtk3

"gtk2 or gtk3"? This sounds strange. Not only because it obviously
doesn't work, but also because x2gomatebindings ships a *library* which
links to GTK2. Even if the or-dependency would have worked, gtk3 as the
only installed package would have left x2gomatebindings (theoretically)
in a broken state.

Luckily, though, RPM automatically adds dependencies on other packages*
for libraries, by examining what libraries are being linked after
destrooting. Thus, gtk2 will always be pulled in automatically**.

The Requires: statement was semantically thus redundant in the best case
and incorrect/causing breakage in the worst case.



Mihai

*) this mechanism will not catch libraries loaded at run time via
dlopen() for instance. This is mostly used for modules. One example of
software making heavy usage of that is wine.
**) I'm making a mental note here to revisit this issue. While run time
dependencies are automatically added *for libraries*, BuildRequires
still need to be set correctly or building the package will fail.