sed magic in the Makefile sounds fine.

In NetBSD pkgsrc, multiple versions of python can be installed at the same 
time. They are called python2.4, python2.5, ...; also multiple versions of 
python modules can be installed, once per python version.

Also, pkgsrc doesn't install into /usr, but /usr/pkg by default.

I can't talk about other packaging systems or Linux distributions, but I
think pkgsrc isn't the only one that does it like that, since I've seen
support for similar schemes in quite a few programs. They usually check
for a usable python interpreter in the configure phase and then use it
during installation.

So my suggestion is checking for the existence of python, python2.4,
python2.5, python2.6 (python3.0/3.1 if supported), overridable from the
environment (e.g. ${PYTHONBIN}) and making a rule that replaces the
interpreter in the installed files with the found python executable.

zeitgeist-0.2.0: using "env python" instead of python executable name
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for Zeitgeist Framework.

Status in Zeitgeist Framework: Incomplete

Bug description:
The configure script finds out the name of the python executable, here 
However, the two scripts zeitgeist-daemon and zeitgeist-datahub use a hardcoded 
"/usr/bin/env python" in their shebang lines. Please substitute "${PYTHON}" 
there instead.

Mailing list: https://launchpad.net/~zeitgeist
Post to     : zeitgeist@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zeitgeist
More help   : https://help.launchpad.net/ListHelp

Reply via email to