zeitgeist-project.py shouldn't look at _config.py

Bug #661282 reported by Siegfried Gevatter
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Zeitgeist Framework
Invalid
Undecided
Unassigned

Bug Description

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.

Revision history for this message
Siegfried Gevatter (rainct) wrote :

Never mind.

Changed in zeitgeist:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.