https://bugzilla.novell.com/show_bug.cgi?id=894588
https://bugzilla.novell.com/show_bug.cgi?id=894588#c1
Rolf Krahl changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rolf@rotkraut.de
--- Comment #1 from Rolf Krahl 2014-09-02 13:08:03 UTC ---
I did a little digging into the problem, so here is what I found so
far. Unfortunately things are a little complicated upstream.
Normally, a Python source distribution provides a setup.py script.
You run "python setup.py install" and the script should build and
install everything where it belongs. This also generates and installs
the egg-info for the package.
In this case, the PySide source distribution[1] is composed of
subpackages, pyside, pyside-tools, and shiboken. It contains not only
the Python package, but also C++ libraries and header files, command
line tools and more. The subpackages are also available separately in
own source distributions. The content of these separate source
distributions is the same as the content of the sub directories in the
top level distribution. Building is controlled using cmake. The top
level source provides a setup.py script, but the separate source
distributions of the subpackages do not contain one.
The openSUSE packages python-pyside and python-pyside-shiboken in
Factory and 13.2 (and python-pyside-tools in KDE:Qt) are based on the
respective subpackage source distribution. Since there is no
setup.py, they call cmake and make directly. This installs everything
nicely in the right place, but doesn't bother creating the egg-info.
If one takes the top level source distribution instead and runs the
setup.py, this does create and install the egg-info. But it screws up
most of the rest: libraries and header files are placed in the wrong
location (in the Python package dir in %{python_sitearch}), other
stuff is not installed at all. So the result of this approach is
basically unusable.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
