On Thu, Mar 11, 2004 at 04:25:47PM +0100, Sven Neumann wrote:
> Hi Dave,
>
> Dave Neary <dneary@xxxxxxx> writes:
>
> > We should just say that GTK+ 2.4 is not out yet, and we can't base
> > stable software on an unstable toolkit. Especially since we've been in
> > a pre-release freeze for 3 months.
>
> By the time that GIMP 2.0 is release, GTK+ 2.4 will be released as
> well. We might be able to be release a few days earlier, or it might
> happen the other way around.
>
Agreed, but the filechooser is still under development/testing.
> > > If we do that we will most likely very soon
> > > see binary GIMP2 packages showing up that have these patches included.
> > > Mitch, what do you think? Would that be a problem at all?
> >
> > I doubt that. Especially since the sources we'll provide will only
> > require gtk+ 2.2. The target, I guess, is to have a GIMP based on 2.4
> > around the time where distros start shipping GNOME 2.6. Which will
> > probably be towards the end of the Summer.
>
> Distros will start shipping GNOME 2.6 shortly after it has been
> released and the release schedule for GNOME 2.6 says March 22nd. This
> date will have to be corrected due to the delayed GTK+-2.4 release but
> I think we can expect a GNOME 2.6 release in early April.
>
> Thus, we should face the fact that at least some distros will make
> their GIMP 2.0 packages depend on GTK+-2.4 and ship with these patches
> applied.
>
I don't see a problem with this. As long as the distros maintain their
patches themselves. I don't really know how Mitch's patch works, but
may be it could be included with some #ifdef GTK2_4. This way, we could
release a gimp-2.0.1 with or without support for filechooser.
DindinX
--
david@xxxxxxxxxxx
i;main(b,v)char**v;{char t1['e'],t2['e'],*p;strcpy(t2,v[1]);while(strlen
(t2)<50){puts(strcpy(t1,t2));for(p=t2;t1[i];p+=2)for(*p=49,p[1]=t1[i];t1
[++i]==p[1];(*p)++);*p=i=0;}}
