Hi, I've recently upgraded to python 2.3, and running the updater tool I've seen that python-2.2 paths are hardcoded in the current lintool -0.2.4 installation method. Here is a setup.py file to replace the current Makefile, and an ebuild updated accordingly. PS: yes, I know lintool is deprecated, but since it is still in the tree and some people may, like me, still have it on their system, it's not completly useless to make it install correctly... is it? PS 2: is there a mail alias for the new portage tools herd, to assign this kind of reports? Reproducible: Always Steps to Reproduce:
Created attachment 20910 [details] files/setup.py-0.2.4
Created attachment 20912 [details] lintool-0.2.4-r1.ebuild Based on 0.2.4-r1, but now using distutils.eclass. I think you don't need to revision-bump it since: - people running python-2.2 don't have any trouble - the python updater script try to reinstall the exact already installed version, hence, overwriting the -r1, you ensure it will be updated when really needed. Only people already running python-2.3 may miss it, but this ones know what they do, right?
I ran into that problem today. The best would be to change the Makefile to check which python version is installed. A quick hack would be: DEPEND="=dev-lang/python-2.2"
> A quick hack would be: DEPEND="=dev-lang/python-2.2" That would work: python 2.2 and 2.3 are in different slot. If you install 2.2 and then 2.3, your "=dev-lang/python-2.2" dependency will be satisfied, but the install will still be broken because 2.3 will be the default for /usr/bin/python. > The best would be to change the Makefile Patching the Makefile is an option, but why implementing an adhoc fix whereas the distutils eclass already has the generic fix for modules that come with a setup.py file? Did you have troubles with this second solution (using the setup.py and ebuild I've attached)?
added a patch to lintool to make this work with python-2.3
