The fluxspace ebuild should choose the correct paths based on currently used python version. This will make sure it installs correctly when when the python 2.3 update happens at some point. It will also bring the dependencies and the code in src_install() more in line with each other. I will attach a diff for an updated ebuild doing just that. Reproducible: Always Steps to Reproduce:
Created attachment 18172 [details, diff] Removes hardcoded python2.2 paths
This works, but looks pretty messy to me. This should really be handled ideally by the upstream fluxspace guys, and less ideally agreed upon by our own python team. Comments you guys?
The fluxspace website says it depends on python and is tested with version 2.2, so I agree it might be messy allowing any python version. But I don't think the current ebuild is much better than this. a. it has DEPEND=">=dev-lang/python-2.1" b. src_install contains "dosym /usr/lib/python2.2/site-packages/fluxspace.py .." I still think this is messy and should be corrected. In my opinion we have two options: 1. set DEPEND="dev-lang/python-2.2*" (as per the website) 2. remove hardcoded paths from src_install (as per my patch or another cleaner patch if somebody offers one)
http://sourceforge.net/tracker/index.php?func=detail&atid=548097&aid=826379&group_id=76737 Giving that a try, but upstream doesnt seem very active..
we will monitor any upstream activity (see comment #4)
