Replace old datahub with vala port

I thought about this bug a bit last night, and I think I changed my mind a bit.
1.) yes, we should remove the python datahub from lp:zeitgeist entirely
2.) no, we should not do it ASAP, we should wait for it until ubuntu maverick got released. Two reasons for this: a.) I doubt the vala datahub will make it into maverick (they are in a frozen freeze right now), b.) I don't want to maintain two versions of the same software at the same time. This makes this bug a first target for a 0.6 release we could try to publish somewhere at the end of october.
3.) with this change we should remove the '--no-datahub' switch of the daemon and replace it by '--use-datahub </path/to/datahub>'

+1 I agree completely with you

On Tue, Sep 7, 2010 at 11:09 AM, Markus Korn <email address hidden> wrote:

> I thought about this bug a bit last night, and I think I changed my mind a
> bit.
> 1.) yes, we should remove the python datahub from lp:zeitgeist entirely
> 2.) no, we should not do it ASAP, we should wait for it until ubuntu
> maverick got released. Two reasons for this: a.) I doubt the vala datahub
> will make it into maverick (they are in a frozen freeze right now), b.) I
> don't want to maintain two versions of the same software at the same time.
> This makes this bug a first target for a 0.6 release we could try to publish
> somewhere at the end of october.
> 3.) with this change we should remove the '--no-datahub' switch of the
> daemon and replace it by '--use-datahub </path/to/datahub>'
>
> --
> Replace old datahub with vala port
> https://bugs.launchpad.net/bugs/630593
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Zeitgeist Framework: New
> Status in Zeitgeist Datahub: New
>
> Bug description:
> Now with mhr3's vala datahub port, I think we should get rid of the python
> version ASAP.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/zeitgeist/+bug/630593/+subscribe
>

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

> 3.) with this change we should remove the '--no-datahub' switch of the daemon and replace it by '--use-datahub </path/to/datahub>'

I think this is not necessary, the vala port uses the same binary name and is installed in /usr/bin, so it'll work exactly the same, moreover I don't think anyone is going to put effort to properly split out the python datahub to have it available as a standalone app (so one could choose which datahub to use).