← Back to team overview

zeitgeist team mailing list archive

Re: [Bug 483556] Re: Make the loading of extensions to the engine configurable

 

OK I withdraw my statement

On Tue, May 25, 2010 at 6:27 PM, Mikkel Kamstrup Erlandsen
<mikkel.kamstrup@xxxxxxxxx> wrote:
> Technical note: GSettings is a part of GLib, specifically GIO, and will
> not as such incur a new dep., except requireing a very recent GLib
> binding. However I am not sure we'll see bindings before we migrate to
> an introspection-backed Python (PyGI).
>
> But overall my opinion is simply that we must minimize the number of
> files to parse or stat during startup.
>
> --
> Make the loading of extensions to the engine configurable
> https://bugs.launchpad.net/bugs/483556
> You received this bug notification because you are a bug assignee.
>
> Status in Zeitgeist Framework: Confirmed
>
> 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.
>
>
>
>


-- 
This is me doing some advertisement for my blog http://seilo.geekyogre.com

-- 
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: Confirmed

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