Fwd: gtk+ API change; who should fix it? (A.k.a. Why isn't GNOME 2.19.4 released yet?)
- From: "Elijah Newren" <newren gmail com>
- To: "GTK+ development mailing list" <gtk-devel-list gnome org>, pygtk <pygtk daa com au>
- Subject: Fwd: gtk+ API change; who should fix it? (A.k.a. Why isn't GNOME 2.19.4 released yet?)
- Date: Thu, 21 Jun 2007 20:07:45 -0600
Just realized that pygtk and gtk-devel-list subscribers may not be on
d-d-l. So I'm forwarding this. See
http://mail.gnome.org/archives/desktop-devel-list/2007-June/msg00109.html
for the thread and discussion. Please jump in.
---------- Forwarded message ----------
From: Elijah Newren <newren gmail com>
Date: Jun 21, 2007 8:05 PM
Subject: gtk+ API change; who should fix it? (A.k.a. Why isn't GNOME
2.19.4 released yet?)
To: Gnome Desktop Development List <desktop-devel-list gnome org>
Hi,
As noted in bug http://bugzilla.gnome.org/show_bug.cgi?id=449318,
there was a recent gtk+ API change. jdahlin just barely told me that
the changed API has existed since 1998, long before gtk+-2.11.x (and
pointed me to http://bugzilla.gnome.org/show_bug.cgi?id=447214). This
API change breaks pygtk and means that much of GNOME cannot be
compiled. But it doesn't seem clear who should fix this. Should gtk+
revert it or somehow fix the API break, or is this an API break we
want and expect pygtk to adapt to?
Elijah
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]