On Mon, Dec 22, 2003 at 06:15:17PM +0100, David Neary wrote:
> Not at all. GTK+ lived in the GIMP source tree until it was
> capable of being a standalone project. Afterwards, its main
> developers were gimp developers. Unfortunately, several of them
> followed the path which GTK+ has become to go on to be core GNOME
> developers and no longer work on the GIMP. 
> The point is that as it is, gegl is not a standalone project. It
> doesn't seem to me like it is mature enough that if the GIMP went
> under (say a few more people quit), gegl would not go on to be a
> standalone graphics library in the way that gtk+ went on to be a
> standalone toolkit. During the incubation of the project, it
> needs attention from us in the same way as gtk+ got attention
> pre-1.0. 

But it *is* a standalone project. That's been the intent from the beginning.
I don't see how "incubation" helps it in any way. There are people who
have indicated wanting to use it for other projects besides GIMP already.
GTK+ was distributed as part of GIMP until people found out that "hey, this
is a useful general purpose toolkit". We already know that with GEGL. There
weren't any notable positive benefits with keeping GTK+ as part of the GIMP

> > GEGL is a separate project and it is IMO very important that it
> > doesn't become too GIMP-centric. Having it included in the GIMP
> > tarball will make it appear as part of The GIMP which it isn't
> > supposed to be. What you suggest basically has only disadvantages. Let
> > alone the fact that it will be a nightmare to maintain.
> I'm not suggesting maintenance. I'm suggesting including
> milestone releases of gegl in our sources. Or storing them with
> our release tarballs. Either is good. Basically, releasing them
> together. Early. Before we use the functionality. So that they
> get built, and people are aware that gegl is real software, not a
> mission statement from 3 years ago. I'd like to see this done
> hand-in-hand with a configure check for gegl, so that we actually
> do get people downloading and building it.

There isn't any point. The problem with dependencies most people have is
not downloading and installing tarballs, but rather the mess that is
Freetype library incompatibilites and by extension any of the things
that directly depend on it.

GEGL doesn't depend on any external library GIMP doesn't already need.

Gimp-developer mailing list

Reply via email to