On Sat, Jun 20, 2009 at 3:06 PM, Andre Klapper<ak-47 gmx net> wrote:
I can see several options here:
* This is a problem of those older distros and upstream gtk+ does
not need to care about it
* If'def a lot of code in the affected modules
* Introduce those API additions to upstream gtk+ 2.12.x and
publish a 2.12.13 tarball
No, GTK+ 2.12 is a stable (in fact, even a dead) branch at this point,
that we are not going to open up for new API at this point. The idea
of stable branches in GTK+ is that you can rely on the fact that if it
built against 2.x.y, it will also build and work against 2.x.z with z
< y.
Nevermind that enterprise distros are unlikely to follow such an
unprecedented stability-breaking late release anyway...