Bug#290811: libglade2 toolbar problems should be fixed in applications

[Andreas Rottmann]

Margarita Manterola <marga@marga.com.ar> wrote:

> Hola Ross Burton!
> 
>> What about glade files and applications which expect the new API to be
>> used?  The problem is that the two APIs cannot be mixed, so will this
>> change just result in a different set of applications breaking?
> 
> If there are applications that use the new api directly, yes, they will be
> broken.  The fact is that we are really close to the famous sarge freeze,
> and if other applications break because of this, they probably won't be
> allowed to enter sarge.  After Sarge is released we can go and ask all the
> applications to update their API (I guess).
> 
I think meld should be fixed to work with the new libglade, instead of
the other way around (quoting from [0]):

[0] http://bugzilla.gnome.org/show_bug.cgi?id=160586

,----
| libglade-2.4.1 is building toolbars using the new GtkToolbar API.
| Meld is then adding some buttons to the toolbar with the old API
| (append_element).  If you use the new toolbar APIs, things should
| work fine.
| 
| You might need to open/save your project in a new version of glade
| to upgrade the toolbars to use GtkToolButtons.
`----

It is no viable strategy to release with a libglade2 that has
incompatible behaviour to upstream. Just think of a user compiling
software locally that relies on the changes made in libglade
2.4.1. Also, it seems synaptic, which also had this issue (see
#288642) has already been fixed, as has the Linux kernel's gconfig
system.

So, I've you cannot convince me that libglade2 should be patched (I
think you won't be able to :-P), I'll reassign #290811 this to meld.

Regards, Rotty
-- 
Andreas Rottmann         | Rotty@ICQ      | 118634484@ICQ | a.rottmann@gmx.at
http://yi.org/rotty      | GnuPG Key: http://yi.org/rotty/gpg.asc
Fingerprint              | DFB4 4EB4 78A4 5EEE 6219  F228 F92F CFC5 01FD 5B62

Say NO to Software Patents! -- http://petition.eurolinux.org/