Hi all, I've spent the past couple of days getting PySide to build and run on Nemo. To generate the PySide bindings a tool called Shiboken is used (similar to swig, Boost.Python, etc.). There's currently a Shiboken package in CE:Apps, but it's 8 months old and seems to be broken. Its -devel package depends on libshiboken1, which never gets generated, so it's not possible to actually build anything against it.
I've built an updated version of Shiboken (with a slightly different naming convention, python-pyside-shiboken instead of simply shiboken, derived from the OpenSuSE naming convention) which seems to work fine and allows PySide to be built against it without any trouble. From what I can see it'd seem more appropriate for Shiboken and PySide to be in CE:MW:Shared than in CE:Apps, since they're not really end user applications, and PySide depends on phonon which is provided by CE:MW:Shared, so they couldn't really go in any lower level repository. So my proposed solution would be that the current Shiboken package is removed, and then I put in pull requests for my Shiboken and PySide packages to CE:MW:Shared. As far as I'm aware there's unlikely to be any packages that depend on the current Shiboken version, since it's mainly only used for building PySide (it's a PySide sub-project). But I'm pretty new to Mer and Nemo, so could easily be mistaken about these things. Both packages are in my OBS repository, along with a PySide application (Tizmee) that I used to make sure the generated bindings worked: https://build.pub.meego.com/project/show?project=home%3Aelleo Thanks, Mike.
