Bug 135250 - Please split PyQt from kdebingdings-python
Summary: Please split PyQt from kdebingdings-python
Status: VERIFIED FIXED
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: X11 Applications (show other bugs)
Version: unspecified
Hardware: All SuSE Linux 10.0
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Stephan Kulow
QA Contact: Stefan Dirsch
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-23 00:01 UTC by Kurt Garloff
Modified: 2005-12-20 23:21 UTC (History)
1 user (show)

See Also:
Found By: Third Party Developer/Partner
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kurt Garloff 2005-11-23 00:01:47 UTC
Little GUI applications that use the Qt bindings of python used to require
python, qt and PyQt. These days, the PyQt bindings are part of kdebindings-python which require kdelibs which require a lot of libraries.

Not a desirable solution. On your GNOME desktop, you may want to limit the amount of installed KDE packages and still run the hp-toolbox from hplip.
On a virtual machine, you may want to have a simple GUI (which I would recommend to do with PyQt) without a full-blown KDE desktop.

Please split off the PyQt part again.
Comment 1 Stephan Kulow 2005-11-24 15:19:10 UTC
done
Comment 2 Johannes Meixner 2005-11-25 08:37:32 UTC
In kdebindings3-python.spec there is now
---------------------------------------------------------------------
%files -n python-qt
%defattr(-,root,root)
%dir /opt/kde3/share/sip
/opt/kde3/share/sip/qt*
/usr/%_lib/python%{py_ver}/site-packages/pyqtconfig.py
/usr/%_lib/python%{py_ver}/site-packages/qt*
---------------------------------------------------------------------

But as fas as I know at least
/usr/%_lib/python%{py_ver}/site-packages/sip.so
/usr/%_lib/python%{py_ver}/site-packages/sipconfig.py
are also needed.
Comment 3 Stephan Kulow 2005-11-25 09:09:45 UTC
do you have a way to test it?
Comment 4 Stephan Kulow 2005-11-25 09:13:33 UTC
awaiting /work/built/mbuild/portia-coolo-6/ :)
Comment 5 Johannes Meixner 2005-11-25 09:20:52 UTC
I test whether /usr/bin/hp-toolbox still works.
When I call it from a terminal window without sip.so I get:
---------------------------------------------------------------
jsmeix@nelson:~> hp-toolbox
Traceback (most recent call last):
  File "/usr/bin/hp-toolbox", line 41, in ?
    import base.async_qt as async
  File "/usr/share/hplip/base/async_qt.py", line 85, in ?
    from qt import *
ImportError: No module named sip
---------------------------------------------------------------
/usr/bin/hp-toolbox does not need sipconfig.py to run
but I think when pyqtconfig.py is included it makes sense
to have sipconfig.py also included.

Kurt Garloff wrote in a mail to me:
------------------------------------------------------------------
My own PyQt apps work with only sip.so, pyqtconfig.py and qt*.so.
------------------------------------------------------------------
but I don't know what Kurt's own PyQt apps are.
Comment 6 Kurt Garloff 2005-12-20 16:12:09 UTC
I also vote for including sipconfig.py and sip*.so.
The latter is needed for my PyQt app as well.
Comment 7 Stephan Kulow 2005-12-20 18:17:24 UTC
did you test the new version at all?
Comment 8 Kurt Garloff 2005-12-20 23:21:27 UTC
Man, it's d*mn difficult to get an X export working from a chroot.
Next time, I'll create a virtual machine ...

I tested: The python-qt package does now contain everything that's needed
AFAICS.

Thanks!