|
Now Shipping Version 8.0
|
SearchBook navigationDonatePlease make a donation to help fund SimplyMEPIS development. |
Freevo, HPLIP and PythonOut of curiosity, has anyone else installed Freevo along with it's Python 2.3 dependencies and ended up killing HPLIP? I've done this twice so far and managed to fix HPLIP each time. However, I do have some strange happenings with HPLIP but I'll work these out later. Michael »
|
Buy From MEPISView your shopping cart
When you buy products directly from MEPIS, you help support the further development of SimplyMEPIS. MEPIS LLC Bus Phone: +1.304.288.0993 We accept orders by mail if paid by US check or by money order on US funds. Please note, we are NOT able to accept credit card orders by phone.
|
|
|
Michael, at this time Debian
Michael, at this time Debian has some broken packages in both Python and printing and it looks like Ubuntu is not checking for those things, I hope you get it sorted, trying different versions may help.
regards,
Jimmy
Microsoft Windows - code name "The Beast" RC-1
INTEL P-IV/HT 3.0GHz - 2X256 DDR3200 - SimplyMEPIS 6.0-1
KDE 3.5.4 - kernel 2.6.15-23-686-SMP - My iMAC runs Debian, Sarge
FreevoAptUbuntu
Michael, have you seen this page: http://freevo.sourceforge.net/cgi-bin/doc/FreevoAptUbuntu
regards,
Jimmy
INTEL P-IV/HT 3.0GHz - 2X256 DDR3200 - SimplyMEPIS 6.0-1
KDE 3.5.4 - kernel 2.6.15-23-686-SMP - My iMAC runs Debian, Sarge
Here's what happened to me.
I know there are some strange things in Debian with Python but I've stumbled across this SNAFU and am wondering if anyone else has gotten bit by this.
When installing Freevo 1.5.x, Python 2.3 is required. Installing Python 2.3 doesn't break anything but it doesn't allow Freevo to run either since it launches using the "/usr/bin/python" symlink. That symlink points to "/usr/bin/python2.4". Fixing the symlink to point to "/usr/bin/python2.3" breaks HPLIP.
The HPLIP tools use "#!/usr/bin/env python" as their method to link to the "correct" version of python which, upon installing Python 2.3 and fixing the symlink, is now incorrect.
I fixed this by editing the HPLIP tools by changing "#!/usr/bin/env python" to "#!/usr/bin/python2.4". I'm thinking I'm going to have to edit the entire Freevo 1.5.x installation so it uses Python 2.3 directly (/usr/bin/python2.3) and return the symlink to it's former state. I'd like to avoid this since Freevo is a rather large program suite.
I know it's common programming practice to call your interpreter by it's common name rather than specific simply because "we've always done it that way." This is a prime example of why NOT to do things this way. Multiple installations of Python on the same machine and differing programs that require each version yet use the same symlink to launch tends to wreak havoc on a user. Even some veteran users would be lost trying to solve this one.
Michael
=====================================================
"Reality? Oh, yeah. That has nothing to do with me."
symlink
to get freevo to run (on the older debpackages) I had to symlink python2.3 to python.
as i haven't got anything else wanting 2.4 python i haven't had to alter anything else to keep things working on that machine
HPLIP requires Pytho2.4
HPLIP is the only thing I've found so far that requires Python2.4 via the /usr/bin/python symlink.
I installed the 1.5.4 DEB package for Freevo, which has Python 2.4 support built in, and corrected the /usr/bin/python symlink. Everything seems to be fine.
This is one of those oddities where "common" programming practice sneaks up and bites you.
Michael
=====================================================
"Reality? Oh, yeah. That has nothing to do with me."