- 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
Created attachment 357956 [details] build.log From the build log: checking for python... /usr/bin/python File "<string>", line 1 import distutils.sysconfig; print distutils.sysconfig.get_python_lib(); ^ SyntaxError: invalid syntax File "<string>", line 1 import distutils.sysconfig; print distutils.sysconfig.get_python_inc(); ^ SyntaxError: invalid syntax File "<stdin>", line 3 print 'yes' ^ [...] * python_mod_optimize(): /usr/lib64/python3.2/site-packages/OpenIPMI.py does not exist Additional info: # eselect python list Available Python interpreters: [1] python2.7 [2] python3.2 * # emerge -qpv openipmi [ebuild R ] sys-libs/openipmi-2.0.18 USE="crypt perl python -snmp -tcl" # qlist openipmi | grep -i python #
Created attachment 357968 [details, diff] openipmi-2.0.18.ebuild.patch - migrate to python-single-r1. Looks like it is hard to build python modules for multiple python implementations - various ebuild cleanups
Created attachment 357982 [details, diff] openipmi-2.0.18.ebuild.patch - use PYTHON_DEPS and PYTHON_REQUIRED_USE - explicitly define pkg_setup()
Created attachment 363962 [details, diff] openipmi-2.0.18.ebuild.patch "python-single-r1_pkg_setup" -> "use python && python-single-r1_pkg_setup"
newer versions were ported to current eclasses