I understand the upstream argument. (Been there, done that.) The GTK folk did not *intend* to break compatibility (at least in a theoretic sense), but did in fact break compatibility (in an actual sense). Their intent was to introduce useful new behaviors into a release meant to preserve old behaviors. Nothing wrong with that. But when it goes wrong, and you *break* applications for thousands of users, you fix it.
Pragmatism wins, or should. Sort of a variant on "the customer is always right" meme. Writing software is not a theoretic exercise. Practical considerations trump. -- Buttons in Eclipse not working correctly with GTK+ 2.18.1-1 https://bugs.launchpad.net/bugs/442078 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
