- 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
we do not need to worry about this at all. We only use python for a few calls over python scripts. We do not care about python version all are supported.
The scripts used by build system don't support Python 3. configure.in contains the following code: MOZ_PATH_PROGS(PYTHON, $PYTHON python2.5 python2.4 python) if test -z "$PYTHON"; then AC_MSG_ERROR([python was not found in \$PATH]) fi When python2.5 or python2.4 are present, then they are used instead of active version of Python (which might be python3.1). The ebuild should export PYTHON variable, so that active version of Python is used.
Created attachment 228323 [details] xulrunner-1.9.2.3-r1:20100418-194108.log This is the build log of installation without any custom changes to the ebuild and when python2.5 and python2.4 are absent.
Created attachment 228327 [details, diff] xulrunner-1.9.2.3-r1.ebuild.patch The patch exports PYTHON="$(PYTHON)", so that active version of Python is checked before python2.5 and python2.4, as was explained in comment #2. 'python_set_active_version 2' causes that PYTHON() function (and other functions not used in this ebuild) print values for active version of Python 2, instead of main active version of Python.
(In reply to comment #4) > Created an attachment (id=228327) [details] > xulrunner-1.9.2.3-r1.ebuild.patch > > The patch exports PYTHON="$(PYTHON)", so that active version of Python is > checked before python2.5 and python2.4, as was explained in comment #2. > > 'python_set_active_version 2' causes that PYTHON() function (and other > functions not used in this ebuild) print values for active version of Python 2, > instead of main active version of Python. > ack feel free to commit it.
Fixed.
