On 2017-08-27 11:00+0200 Ole Streicher wrote:
One point there however remains: I need to support all Python 3 versions we have in Debian; currently Python 3.5 and Python 3.6. The difference are just the shared library stubs, which are compiled using the specific header files (the package will contain both shared libs). Do you have an idea how I could simply do this?
Use multiple builds. Also to make this easier for you I have now (commit e320210) improved user control of the Python version. So for one build you specify -DPLPLOT_PYTHON_EXACT_VERSION=3.5.0 and for the other you specify -DPLPLOT_PYTHON_EXACT_VERSION=3.6.0, and it should "just work" according to my tests of the above commit.
I also have then a question about the dependencies: The old (plplot-10) Debian package had a build dependency on python-gtk2, a package that does not exist for Python 3. I would suspect that it is not needed anymore?
software@raven> find . -type f |grep -v .git |xargs grep -li gtk |less found a large number of files where gtk is mentioned, but none of them are relevant to python. I dimly recall that we used to have a GTK binding that also included a python interface, but that was superseded by the pango/cairo related components of PLplot so is long gone now. So I suspect this build dependency on python-gtk2 is an extremely ancient artifact that you can just ignore from now on.
And, a final point; I think we already shortly discussed that: Debian will drop Qt4 support at some point. Since I am doing a major restructuration of the Package structure anyway, it may be worth to use qt5 only in the plplot package as well; otherwise I would have to do that switching in a few months anyway. Would you agree here?
Our Qt-related components work extremely well with Qt4, and also work pretty well (aside from small character alignment issues and a segfault for pyqt5) with the Debian Jessie version of Qt5. But those Qt5 issues are bound to go away as that library matures (and in fact may have gone away already with the later versions of Qt5 that you have access to with later Debian versions). But I also don't think you should throw away our superb Qt4 capabilities prematurely. So I suggest you use a multiple build approach here as well (one with -DPLPLOT_USE_QT5=ON and one with the default value of that option [-DPLPLOT_USE_QT5=OFF]).
Best regards, and already many thanks for the help!
You are welcome. And thanks very much to you for taking on the responsibility of Debian (and Debian-derived distribution) packaging of PLplot! That job is important because if you make the assumption that the fraction of popularity contest statistics for PLplot represents the fraction of Linux users who actually use PLplot on a monthly basis, then the PLplot users who are using the binary versions of PLplot that you and other packagers (such as Orion for Fedora) are creating far outnumber the ~7000 users who download PLplot each year according to SF statistics. Best wishes, Alan __________________________ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); the Time Ephemerides project (timeephem.sf.net); PLplot scientific plotting software package (plplot.sf.net); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
