Hi! Please find attached pyqwt-5.0.0.ebuild. PyQwt is a set of Python bindings for the Qwt C++ class library and provides widgets for scientific and engineering applications. Remarks: - there is an QA Notice: Pre-stripped files found. PyQwt uses the build tools from PyQt4 and sip which have the same problem. I know how to fix this. - the ebuild does not inherit distutils anymore. The setup.py in the package is only used for generating a source distribution. It is useless for installing PyQwt.
Created attachment 117047 [details] pyqwt-5.0.0.ebuild
pyqwt-5.0.1 is out.
testing this ebuild now (for 5.0.1). just curious, is there any reason it's not slotted differently than pyqwt-4 ?
No, I do not think there is a real reason except that PyQt is not slotted either. FYI: PyQwt-5 works with PyQt-4 and PyQt-3 (configure with '-3' or '--qt3'), but PyQwt-4 works only with Qt-3. Look also at the qwt ebuilds: there exists x11-libs/qwt/qwt-5.0.2-r1.ebuild which builds against Qt-4 and x11-libs/qwt-qt3/qwt-qt3-5.0.2-r1.ebuild which builds against Qt-3. Gerard
Gotcha, so we really need a pyqwt-qt3 package to replace pyqwt 4.
If you like. When you do that, then you need to patch configure/configure.py, something like this: if options.qwt_sources: # yes, zap all occurrences of a qwt library while options.extra_libs.count(qwt): options.extra_libs.remove(qwt) elif qwt not in options.extra_libs: # no, add the qwt library if needed # for Gentoo pyqwt-qt3 ebuild options.extra_libs.append('qwt-qt3') # instead of # options.extra_libs.append(qwt) Gerard
ok, thanks. My thought now is to go ahead and slot pyqwt-5 into SLOT=5. This will allow you (the end user) to keep pyqwt-4 still installed until you can transition to pyqwt-qt3. Then, we can eventually remove pyqwt-4 and qwt-4 from portage. Think that will be okay?
Yes, as far as I understand it will work out that way (I am no Gentoo expert). However, I think that the package naming and slot policy of Qwt is a bit strange (qwt5-qt3 is the natural successor of qwt4 since both depend on Qt-3). Suppose you have to live with it -- Gerard
I agree it's strange. The alternative (from qwt perspective) was to use use qt3/qt4 use flags and compile qwt-5 for either qt3 or qt4. But then problem with that is that you can only have one or the other, but not both at the same time, and packages that depend on qwt then have to check to see which way it was compiled in order to know how they should compile. So if you were to install qt4-qtruby, for example, it may see that you have qt4 installed, but then do a check for qwt-5 and find that you have it only installed for qt3 and not qt4. That makes a bit of a mess. The way it is now is more deterministic, because qwt-5 will always be built for qt4.
Closing bug since pyqwt-5.0.1 is in the tree. Thanks.
