Comment # 2 on bug 949983 from Dominique Leuenberger

Fully agree, fixing the actual reason why the Leap package behaves so different
than the TW one would be the best approach.

the fact that it's appdata / mimehandler is not even that special here (it's
just symbols)

for appdata, there is a /usr/lib/rpm/appdata.prov (with respective fileattrs)
installed, which is very simplistic. For the mime-handler, it's similar
simplistic.

Now, what seems to happen is that on Leap with rpm 4.11.x, those additional
handlers are not run (maybe due to %define _use_internal_dependency_generator
0, which would make sense), but on Leap they are running (And adding their
needed stuff).

So, things to verify here are:

* is %define _use_internal_dependency_generator 0 really behaving different
between Leap and TW (rpm 4.11 vs 4.12)
* Is it actually still valid to disabled the internal dependency generator?
* If really nothing else works (or time does not permit), then we should go for
the work around (but still attempt to fix the issue later one), using:

# Those should be added automatically due to the mere presence of
/usr/share/appdaya/firefox.appdata.xml
Provides: appdata()
Provides: appdata(firefox.appdata.xml)