(For those not familiar with it, CrunchBang is basically a preconfigured Debian Squeeze.)
So a while back, I was writing a script and wanted to use a Python feature introduced in 2.7. Since the latest version I could get from Debian Squeeze's apt repo is 184.108.40.206, I decided to download the latest source and build it myself. After wrangling dependencies myself, I finally got something working, and finished my project.
However, since then, a number of system scripts have stopped working. I noticed that they (the now broken scripts) all start with
#!/usr/bin/env python and depend on one or more things that have been installed by apt-get/synaptic, but are associated with Python 2.6. A few I've fixed by manually changing the header to
#!/usr/bin/python, but now I'm starting to wonder
- Is this normal for people that roll their own Python?
- Did I compile/set up 2.7 wrong somehow?
- Is it unreasonable to expect packages installed with apt-get/synaptic to 'lock in' with the version of dependencies they were installed with?
- Should I somehow reconfcd /igure my $PATH so that the
/usrfile is found before the
- Should I just delete the hardlink file /usr/local/bin/python and have all of my scripts start with
- Do I have to manually install all of the missing libraries, etc. for
/usr/local? If so, what's the best way to do this?
- Should I file bugs with the package maintainers, projects themselves, or both?
 Which, because of how my path is set up, invokes my
/usr/local/bin/python (2.7) rather than the system's