nautilus-extensions C code imports gi._gobject, but it's an inline macro
so it doesn't get automatic dependencies generated based on DT_REQUIRED.
This commit adds appropriate requires on either python2-gobject or
python3-gobject depending on the version of Python nautilus-python is
compiled with.
It's too late to make the switch now for F29 and ensure that all
packages are compatible. This commit adds an rpm conditional to build
with Python 2 on F29 and older, and use Python 3 on F30 and later.
https://bugzilla.redhat.com/show_bug.cgi?id=1636626
Remove %check section that's disabled; if someone wants to resurrect it
(and make it work) it's available here in the git history.
Remove manual "Requires: pkg-config" that's autogenerated by the
pkg-config dep gen, rename things a bit to make the spec file more
readable.
Commit 566e5e3 incorrectly renamed the binary package from
nautilus-python to python2-nautilus. The python2-/python3- naming scheme
applies to python modules, but nautilus-python is not a python module,
just a library that happens to link with python. It also doesn't support
parallel install for different Python interpreter versions, so it
doesn't make sense to ship both python2-nautilus + python3-nautilus.
Instead of the python module naming guidelines we should just follow
regular app naming guidelines (just use the upstream name).
This commit renames the binary package back to nautilus-python (and the
-devel package as well), obsoleting python2-nautilus,
python2-nautilus-devel, python3-nautilus, python3-nautilus-devel.
The plan is to continue using Python 2 for F29, and switch to Python 3
in F30.
See the discussion in https://bugzilla.redhat.com/show_bug.cgi?id=1636626