in /etc/bashrc, the global system fileThanks - should've thought of looking there
I'm getting close to being able to post an hplip extension (cups-1.2.11, hplip-2.7.6) - I was thinking to post the extension in several parts, does this make sense:
1. hplip.tar.gz - the main programs (cups, espgs, hplip), libs, foomatic, fonts, etc 2. python.uci - v2.3.6 with the latest security updates 3. hplip_etc.dsl - conf files to be loaded once to /etc then added to backup 4. hplip_ppd.tar.gz - ppds to be loaded once then appropriate printer(s) added to backup 5. site-packages.tar.gz -files shared by hplip & python
The locations of the files would be /opt/hplip, /opt/python & /opt/site-packages - once tested, hplip & site-packages could also be uci extensions.Hello Juanito: Do you think my 'MyDSL->Testing->python2.5.uci' could do the job? It is using an idea similar to yours - mine is using '/opt/py25/site-packages' instead of '/opt/site-packages'. Reason is because some python packages want to have '/opt/py25/include' or /opt/py25/share'. Anyway, that is the technical issue. The non-technical issue is that I thought '/opt/site-packages' might conflict with other python uci's - maybe people will want to make uci's for python 2.3 or 2.4. I am saying this because I think you will run into the same problem. If this post seems very rude to you, please forgive me. I do not mean to say that you 'should not' make another python extension. Only, to avoid confusion, I would like to suggest - maybe name it 'python2.3.uci'? Thank you very much.
Quote
Do you think my 'MyDSL->Testing->python2.5.uci' could do the job?
I'm not sure, it might - in fact, I started to work on compiling hplip before you posted your extension (I originally used Roberts extension). Then, because like you, I needed /site-packages outside the uci I re-compiled Python-2.3. In the end I actually needed /extensions outside the uci as well (for the scanning PIL files) but but I put these in /site-packages.
I believe hplip would compile different *.py files against Python-2.5 and I also believe the location of Python might be hardcoded in hplip.
As you say, having the extension use /opt/python2.3 and /opt/python2.3_site-packages or similar would probably make more sense - I'm not sure I can face recompiling things at the moment though...
Quote
in /etc/bashrc, the global system file
I tried changing the path statement and adding the file to my backup - after reboot, even though the modified file is present, the path has not changed. I guess this means the the path is set before the backup is restored?
Quote
Do you think my 'MyDSL->Testing->python2.5.uci' could do the job?
I tested your extension with hplip - some of the hp functions worked and some didn't, but all of them complained about the changed version of python. I guess I could recompile hplip against your extension but perhaps some other DSL users have a use for the latest python-2.3, so I'll take the easy way out. I will however change /opt/python to /opt/python-2.3 and /opt/site-packages to /opt/py-2.3/site-packages so the different versions don't tread on each others feet - how does that sound?Next Page...
original here.
