** Changed in: zeitgeist
Status: New => Invalid
zeitgeist-project.py shouldn't look at _config.py
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Zeitgeist Framework: Invalid
When you get a clean copy of the branch and execute Zeitgeist from there, the
configuration from zeitgeist/__init__.py is used, which contains the correct
settings for the daemon running from the branch.
However, once you've run "make" (which is now compulsory, to get the ontology
compiled) a zeitgeist/config.py file is generated (to be installed somewhere in
$PREFIX/). From now one if Zeitgeist is run from the branch it will load this
configuration, which contains paths corresponding to the system-wide install.
This has given me problems in the past (with system-wide extensions being
loaded or something).
I'd propose that we change zeitgeist-daemon.py (vs zeitgeist-daemon) to always
use __init__.py's configuration file.
Mailing list: https://launchpad.net/~zeitgeist
Post to : email@example.com
Unsubscribe : https://launchpad.net/~zeitgeist
More help : https://help.launchpad.net/ListHelp