(Correction: in my previous post "configure time" should be "build time", ie. it's generated when "make" is run).
2009/12/2 Thomas Klausner <t...@giga.or.at>: > Well, then my detailed diagnosis was incorrect; however, the main part was: > it doesn't work. zeitgeist-daemon and zeitgeist-datahub start with "#! > /usr/bin/python", while config.log contains: > PYTHON='/usr/pkg/bin/python2.6' Hmm, no idea why that could happen. Patches welcome. -- zeitgeist-0.2.0: using "env python" instead of python executable name https://bugs.launchpad.net/bugs/401199 You received this bug notification because you are a member of Zeitgeist-Engine, which is the registrant for Zeitgeist Framework. Status in Zeitgeist Framework: Fix Released Bug description: The configure script finds out the name of the python executable, here "python2.5". 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
