Packaging PythonQt for Qt 5

Erik Lundin erik at lists.lun.nu
Tue Jun 6 15:33:44 UTC 2017


Den 2017-05-27 kl. 22:38, skrev Dmitry Shachnev:
> Yes, the soname is something to consider for upstream. If we think upstream
> made an ABI break, we usually do not patch the soname, but instead rename the
> package, i.e. append a prefix (“a” or “v5”).

The new upstream release 3.2 solves this. The produced libraries are now 
(for Python 2.7)

libPythonQt-Qt5-Python2.7.so -> libPythonQt-Qt5-Python2.7.so.3.2.0
libPythonQt-Qt5-Python2.7.so.3 -> libPythonQt-Qt5-Python2.7.so.3.2.0
libPythonQt-Qt5-Python2.7.so.3.2 -> libPythonQt-Qt5-Python2.7.so.3.2.0
libPythonQt-Qt5-Python2.7.so.3.2.0
libPythonQt_QtAll-Qt5-Python2.7.so -> 
libPythonQt_QtAll-Qt5-Python2.7.so.3.2.0
libPythonQt_QtAll-Qt5-Python2.7.so.3 -> 
libPythonQt_QtAll-Qt5-Python2.7.so.3.2.0
libPythonQt_QtAll-Qt5-Python2.7.so.3.2 -> 
libPythonQt_QtAll-Qt5-Python2.7.so.3.2.0
libPythonQt_QtAll-Qt5-Python2.7.so.3.2.0

How can I submit my packaging changes for review? Are you using pull 
requests somewhere?

/Erik



More information about the pkg-kde-talk mailing list