Re: ping for gtk+extra2 removal - implications for libgtkada2 and gpsim
Selon Josselin Mouette <email@example.com>:
> Le lundi 29 juin 2009 à 23:30 +0100, Neil Williams a écrit :
> > On Mon, 29 Jun 2009 23:19:45 +0100
> > Neil Williams <firstname.lastname@example.org> wrote:
> > > gtk+extra2 will FTBFS as soon as the functions that will be removed in
> > > GTK+3.0 become deprecated in GTK+2.0. GTK+2.0 doesn't have to be
> > > removed from Debian for gtk+extra2 to break. Yes, that isn't how
> > > things *should* work and it isn't how other packages *do* work but
> > > gtkextra has been dead upstream for such a long time that bitrot has
> > > all but ensured that this will be the result.
> > Let me clarify that a bit.
> > As soon as you take Josselin's advice for preparing the rest of gtkada
> > for GTK3.0, you'll discover that nothing in gtkextra has been prepared
> > for what is *currently* deprecated in GTK+2.0. Fixing that will mean
> > completing the migration of gtk-extra2 through to current GTK+2.0 as
> > well as implementing the transition in gtkada. This is why I cannot
> > implement Josselin's advice in quicklist - it shows up the breakage in
> > gtk-extra2.
> I think you misunderstood my email. What is currently deprecated in GTK+
> 2.0 *is* what will disappear in GTK+ 3.0. But deprecated doesn’t mean
> the functions will disappear. All the current GTK+ 2.0 API will remain
> available until we remove gtk+2.0 from the archive, even deprecated
So, my understanting was correct then: gtk-extra2 will FTBFS only when you
remove GTK+2 from Debian, not when you introduce GTK+3. Joss, can you tell me
whether you intend for there to be a transition period when both GTK+2 and
GTK+3 are in Debian? My intention is neither to take over maintenance of
gtk-extra nor to remove functionality from GtkAda; rather to try and give a
clear roadmap for upstream to plan the necessary changes, i.e. reimplementing
some of GtkAda's widgets with GTK+3 instead of gtk-extra.