zeitgeist team mailing list archive

[Siegfried Gevatter <rainct@xxxxxxxxxx>]

Public bug reported:

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.

** Affects: zeitgeist
     Importance: Undecided
         Status: Invalid

-- 
zeitgeist-project.py shouldn't look at _config.py
https://bugs.launchpad.net/bugs/661282
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

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.