Autoload extensions

Bug #592600 reported by Mikkel Kamstrup Erlandsen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Zeitgeist Framework
Fix Released
High
Mikkel Kamstrup Erlandsen

Bug Description

(Canonical hat on)

For packaging reasons it would be nice if Zeitgeist would automatically load all extensions found somewhere on the file system so that we could ship the FTS extension in a separate .deb for Unity. In theory it's possible to use the env vars there are, but that will require some nasty tricks in the package afaik.

On a more general note this feature would also make it easier for distributors to ship a clean unpatched Zeitgeist, but sill bundle their own extensions. Fx. MeeGo might want to ship the Tracker extension by default.

Related branches

Revision history for this message
Mikkel Kamstrup Erlandsen (kamstrup) wrote :

From IRC:
<thekorn> kamstrup, for the other bug, would you be happy with a --load_all_extensions commandline switch for the daemon?

I am not sure that is good enough, unless we package ZG to always launch with that. My idea was that simply installing/removing .debs determined which extensions where loaded, to maximize flexibility for ISVs. If ZEITGEIST_DEFAULT_EXTENSIONS where set, this should probably override the ones found on the file system.

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

I think any extensions from inside /usr/share/zeitgeist/_zeitgeist/engine/extensions/ and ~/.local/share/zeitgeist/extensions/ should be loaded by default (or if you prefer, those symlinked in a "active"/"default"/whatever directory within those directories). The ZEITGEIST_DEFAULT_EXTENSIONS variable would only be there for the user to disable some of those (plus we should also add a ZEITGEIST_DISABLED_EXTENSIONS var).

Revision history for this message
Mikkel Kamstrup Erlandsen (kamstrup) wrote :

Tagetting for 0.4.1 as it seems everyone is more or less on the same page

Changed in zeitgeist:
importance: Undecided → High
milestone: none → 0.4.1
status: New → Triaged
Revision history for this message
Markus Korn (thekorn) wrote :

There is one reason why I don't want the daemon to always start with all extensions found in some locations: when developing zeitgeist and running the daemon "from the branch" I want to have complete control over things which are loaded, and I also want to always run a minimalistic version of zeitgeist.

Revision history for this message
Siegfried Gevatter (rainct) wrote : Re: [Bug 592600] Re: Autoload extensions

2010/6/17 Markus Korn <email address hidden>:
> when developing zeitgeist and
> running the daemon "from the branch" I want to have complete control
> over things which are loaded, and I also want to always run a
> minimalistic version of zeitgeist.

So you define the ZEITGEIST_DEFAULT_EXTENSIONS variable which tells it
not to look for stuff by itself.

Revision history for this message
Mikkel Kamstrup Erlandsen (kamstrup) wrote :

Started on this

Changed in zeitgeist:
assignee: nobody → Mikkel Kamstrup Erlandsen (kamstrup)
status: Triaged → In Progress
Changed in zeitgeist:
status: In Progress → Fix Committed
Seif Lotfy (seif)
Changed in zeitgeist:
status: Fix Committed → Fix Released
Changed in zeitgeist:
milestone: 0.4.1 → 0.5.0
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.