Subject: Re: I plan to move AbiGdkPixbuf into the main tree.
From: Dom Lachowicz (firstname.lastname@example.org)
Date: Tue Dec 18 2001 - 08:54:25 CST
Ok, my $0.02 on the issue
GdkPixbuf requires no Gnome Libraries. However, Gnome itself requires
GdkPixbuf, which means that all Gnome installations will ship with a
working copy of GdkPixbuf.
Resolved: on Gnome versions of AbiWord, we should use GdkPixbuf to
import images because it's already there, linked in against our
However, because it has no Gnome dependencies, it would be nice if our
GdkPixbuf loader also was available on non-Gnome platforms for those
persons who want to use it. Further, we do not want to maintain 2 copies
of the same source, because it is a maintance hell.
Resolution: Remove the GdkPixbuf plugin from the main sources in our CVS
tree, and instead only keep the plugin. Henceforth, I now MANDATE that
all future binary releases of AbiWord-Gnome install the GdkPixbuf loader
plugin in the AbiWord-global plugin directory
On Tue, 2001-12-18 at 14:41, Rui Miguel Seabra wrote:
> On Tue, 2001-12-18 at 09:03, Martin Sevior wrote:
> > The plugin is still there. I did not touch that code at all. This is great
> > that you can make it assuming just gdk-pixbuf. Keep doing it. The more the
> > merrier. Everyone is happy.
> So your proposed solution is to keep two copies of the code on two
> different abiword modules?
> 1) src of gdkpixbuf plugin in main module
> 2) src of gdkpixbuf plugin _also_ in plugins module
> 3) 1) and 2) cause a maintenance hell
> 4) previously, gnome AND gtk builds could benefit from the plugin
> 5) removing the plugin from the plugins module will result in that
> only gnome build benefits from the plugin
> I utterly fail to see the benefits.
> Can you please enlighten us all in how can everyone be happy?
> Possible solutions:
> 1) let all be as it is
> maintenance hell
> 2) remove the plugin from the plugins
> The result will be that gtk build will never benefit from the
> plugin unless someone copies it from someplace else.
> 3) remove plugin from main source and let it be on plugins
> The result is that whoever installs abiword (either gnome or gtk),
> would have to install the plugin separately.
> 4) provide an option (ABI_PLUGIN_ABIWORD) so that a gtk build can also
> build the plugin
> I am all for 4 or 3 (by order of best choice), but 1 is unacceptable,
> and 2 is definitely not the way.
> Hugs, rms
> + No matter how much you do, you never do enough -- unknown
> + Whatever you do will be insignificant,
> | but it is very important that you do it -- Ghandi
> + So let's do it...?
This archive was generated by hypermail 2b25 : Tue Dec 18 2001 - 08:53:18 CST