Re: GTK+ branch gyrations

[Christian Dywan <christian lanedo com>]

Am Fri, 7 May 2010 08:49:41 -0400
schrieb Matthias Clasen <matthias clasen gmail com>:

> Since there have been some questions about this recently, here is an
> overview of the current major branches, and where they are heading:
> [...]
> gtk-2-90: This branch has been used to prepare a lot of the
> deprecation removal, etc, for 3.0. I have merged this branch into
> master yesterday, so I consider it closed at this point. Further
> development towards 3.0 will happen on master.
> 
> master: Development towards 3.0, including deprecation removal and new
> features. We have already merged Tristans extended layout work and
> symbolic icon support here, and hope to land a few more things here
> soon, such as improved theme selection
> (http://bugzilla.gnome.org/show_bug.cgi?id=617955) and Carlos' xi2
> input work.

Thanks a lot for merging the branch.

> I'm going to work on doing a 2.90 release off this branch soon. There
> are a number of parallel-install issues to work through before that
> though. Off the top of my head:
> 
> headers: /usr/include/gtk-3.0 ?
> libs: $libdir/libgtk-x11-3.0.so ?
> pc files: gtk+-3.0.pc, etc ?
> modules: stay with $libdir/gtk-2.0 ?
> utilities like gdk-pixbuf-query-loaders: do we need to duplicate these
> ? if we don't change the module location, I think not
> introspection data: Gtk-3.0.gir ?

I think all of the paths/ files with -2.0 in the name which you mention
should be bumped, including the modules because a module compiled
against the new GTK+ won't work with the older one, even if the module
API remains the same.

The utilities don't need to be renamed as far as I see since they
remain compatible and can be used regardless of the ABI of the
binaries.
And if you need to update the loaders for a specific version, you can
pass the modules on the command line.

ciao,
    Christian