zeitgeist team mailing list archive
-
zeitgeist team
-
Mailing list archive
-
Message #01049
[Bug 483556] Re: Make the loading of extensions to the engine configurable
I implemented the behaviour described by Mikkel in comment #17 in revno
1478 of lp:zeitgeist
------------------------------------------------------------
revno: 1478
fixes bug(s): https://launchpad.net/bugs/483556
committer: Markus Korn <thekorn@xxxxxx>
branch nick: trunk
timestamp: Tue 2010-05-25 22:14:11 +0200
message:
Added two new environment variables `ZEITGEIST_DEFAULT_EXTENSIONs` and
`ZEITGEIST_EXTRA_EXTENSIONS` to define which extensions are loaded on daemon
startup. (LP: #483556)
------------------------------------------------------------
** Changed in: zeitgeist
Status: In Progress => Fix Released
--
Make the loading of extensions to the engine configurable
https://bugs.launchpad.net/bugs/483556
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Zeitgeist Framework: Fix Released
Bug description:
right now the relevancy-provider is loaded by default. Unfortunately this extension is kind of buggy and not well tested, so in case of errors while loading this extension the whole engine would fail to run.
We need a configurable plugin-system for our extensions, and for now we should per default disable loading the relevancy provider. If this provider gets more stable we should easily be able to add this extension to the default extensions which are automatically loaded on engine initialization.
References