- If this package can be used as a library and installs Python modules (*.so or *.py) into site-packages directories, then consider supporting installation for multiple Python versions. Please read section "Types of packages" in documentation [1] to decide if this package can support installation for multiple Python versions. - Ensure that the ebuilds do not use deprecated functions or variables. - Please check if Python 3 is supported by this package. You can temporarily set Python 3 as main active version of Python to properly test if this package supports Python 3. - If this package does not support Python 3: - Specify dependency on Python 2. You can use PYTHON_DEPEND helper variable, which should be set before inheriting of python eclass. Please read section "Specification of dependency on Python" in documentation [1]. - If this package cannot support installation for multiple versions of Python, then set active version of Python using python_set_active_version(). - Ensure that shebangs in installed scripts specify correct version of Python. If shebangs are too generic (e.g. '#!/usr/bin/python'), then you can use python_convert_shebangs() to convert shebangs. (Wrapper scripts generated by python_generate_wrapper_scripts() do not require any changes.) Please read section "Shebangs in installed scripts" in documentation [1]. - To ensure that changes applied to the ebuilds are sufficient, please temporarily set Python 3 as main active version of Python and test if this package can be properly installed and if it works at run time. Please see documentation [1] for more details. [1] http://www.gentoo.org/proj/en/Python/developersguide.xml
I've fixed part of this bug with 0.8.1, but there are still a lot of shebangs unconverted (in the custom Makefile's and configure script for build and install process). Somehow "ExactImage.py" doesn't get installed at all(?) now. So, leaving this open.
(In reply to comment #1) > I've fixed part of this bug with 0.8.1, but there are still a lot of shebangs > unconverted (in the custom Makefile's and configure script for build and > install process). Somehow "ExactImage.py" doesn't get installed at all(?) now. > So, leaving this open. > Hi, while 0.8.1 installed just fine on one machine, if failed on a very similar machine with install: target `/var/tmp/portage/media-gfx/exact-image-0.8.1/image//usr/lib64/python2.6/site-packages/' is not a directory: No such file or directory Have you any idea on what might be the reason? Thanks, Helmut.
(In reply to comment #2) It's not related to this bug.
17 Sep 2011; Samuli Suominen <ssuominen@gentoo.org> exact-image-0.8.1.ebuild, +files/exact-image-0.8.1-libpng15.patch: Fix building with libpng15 wrt #383203 by Diego Elio Pettenò
(In reply to comment #4) > 17 Sep 2011; Samuli Suominen <ssuominen@gentoo.org> exact-image-0.8.1.ebuild, > +files/exact-image-0.8.1-libpng15.patch: > Fix building with libpng15 wrt #383203 by Diego Elio Pettenò no idea why you posted that here, or why this was closed... reopening
+*exact-image-0.8.1-r1 (06 Oct 2012) + + 06 Oct 2012; Pacho Ramos <pacho@gentoo.org> +exact-image-0.8.1-r1.ebuild: + Include various fixes from Kevin Pyle, bug #339248. + All its tools look to run on my python3 setup :/
(In reply to Pacho Ramos from comment #6) > +*exact-image-0.8.1-r1 (06 Oct 2012) > + > + 06 Oct 2012; Pacho Ramos <pacho@gentoo.org> +exact-image-0.8.1-r1.ebuild: > + Include various fixes from Kevin Pyle, bug #339248. > + > > All its tools look to run on my python3 setup :/
