python-2.3.4 (but not only this one) uses python2.3 instead of python${PYVER} Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 44140 [details, diff] changes s/2.3/${PYVER}/g additionally the patch begins adding support for nis use flag (not supported by the disable_modules patch yet) omits the pkginst message about python2.2 being installed on the system if this file is not found
Invalid. PYVER is set via calling python. What do you think happens, if you want to install e.g. Python 2.4, but use the 2.3 binary to find out the version number?! If Python is not even installed... ;) I'm not sure about the nis stuff, though.
i think this bug is valid. it just isn't phrased very well. what it is saying is the python-2.3.4 ebuild has references in the ebuild that embeds the python2.3 as the path instead of making it version agnostic. we'll consider this for python-2.4, but don't think we'll be changing 2.3 at the moment. and also becareful that we derive PYVER from ${PV} rather than python eclass. what we prob need is a seperate ebuild local variable for that.
if PYVER is set in eclass and can't be overwritten in ebuild, and it does not mean the current version (not the installed one) than my change is unproper and a new local var as described earlier should be used. My idea was to remove hardcoded versions from ebuild Is the warning about python2.2 valid anymore?
this is fixed in python-2.4 ebuilds, so closing this bug for now.
