On Mon, Dec 19, 2011 at 10:25 PM, Alex Valavanis wrote:
On 19 December 2011 18:02, Alexandre Prokoudine <alexandre.prokoudine@...400...> wrote:
Shipping a safe version of GTK+ internally sounds scary to me. This is exactly what we've been trying to get rid of with even smaller libs such a libgdl and lib2geom. This is where I'd rather see our release manager stepping in to make a decision.
Yeah, I'm not so keen on this either. gdl is only a little library, with just a couple of local changes in our fork, but we've managed to accumulate a pretty big delta against upstream over time. GTK+ is a much bigger library, so it'll be very painful to maintain it. Also, setting a maximum version of a library seems a bit risky - how do we deal with important upstream security fixes, for example?
If this is definitely a known gtk+ issue, do we have an upstream bug we can track? Any idea if there will ever be a fix backported to a release of gtk+ 2, or is this really a case of Inkscape being broken until we reach gtk+ 3 compliance?
I dare say https://bugzilla.gnome.org/show_bug.cgi?id=653437 is the one
Alexandre Prokoudine http://libregraphicsworld.org