Re: Moving some plugins back into the main tree?

From: J.M. Maurer <uwog_at_uwog.net>
Date: Fri Jan 05 2007 - 01:31:10 CET

On Thu, 2007-01-04 at 14:38 -0500, Hubert Figuiere wrote:
> Dominic Lachowicz wrote:
> >
> > Now that libgsf is a requirement and some of our import/export plugins
> > are getting both more popular and more robust (eg. OpenDocument), I
> > was wondering if we might consider moving some of the plugins back
> > into the main tree. I'm concerned that we're making life more
> > difficult for our users than it needs to be.
>
> I don't see the benefit of moving them. Our user get it from
> distributions or installer, that is what matter: what comes pre-build.
>
> The advantage of having them as plugins in the development tree allow:
> 1/ building AbiWord alone and with a selected number of plugins.
> 2/ faster build-test cycles, including better modularisation. Think
> about relinking AbiWord each time you want to test changes to a plugin.

>From a developer and packager point of view, I totally agree with you.

But practically, it is useless to blame a distributor for not packaging,
say, ODT by default. If AbiWord can't handle ODT 'out of the box' from a
users point of view, they will just blame us.

In the end, for me the user's experience is more important that my
developer experience.

Marc
Received on Fri Jan 5 01:31:30 2007

This archive was generated by hypermail 2.1.8 : Fri Jan 05 2007 - 01:31:30 CET