We should include 2.17 in tree, every other distribution is shipping with it. http://www.archlinux.org/packages/extra/i686/pygtk/ http://cvs.fedoraproject.org/viewvc/rpms/pygtk2/devel/ http://packages.debian.org/sid/python-gtk2 It's required by new stable release of media-sound/exaile.
I'm not kind of the "others do it" approach, but if someone has a word with pygtk upstream and they say it's fine, then so be it.
As upstrem states on their website in the about section: "The current version of PyGTK requires at least GTK+ version 2.8.0." So they consider the unstable 2.17.x version as current. Why not place it as ~arch as 2.16 is already arch anyway? And at least even if it's not valueable: 2.17 Works for me :)
uups sry i've missed a 1, its really 2.8 and not 2.18 :/
Hello, Also, PyGTK 2.17 has been released 8 months ago, and no other releases since. So, I suppose that it's not as unstable as they say =D. Since other applications are already using this version, maybe could add it in the tree in ~arch, maybe even masked? Cheers, Raphaël Dehousse
Created attachment 241853 [details, diff] Diff to pygtk-2.16.0-r1 for creating pygtk-2.17.0.ebuild pygtk-2.17.0.ebuild Nothing wrong with it here (amd64, gcc-4.5), at least not yet.
(In reply to comment #5) ebuild diff is not the measure to how much changed in the package... Anyway, seeing that there is pygtk-2.21 out the door, that clearly states that upstream doesn't give a shit about doing releases that follow the rest of the gnome scheme. So if anyone has the time to bump it to 2.17, please do.
+*pygtk-2.17.0 (13 Aug 2010) + + 13 Aug 2010; Gilles Dartiguelongue <eva@gentoo.org> + -pygtk-2.14.1-r1.ebuild, -pygtk-2.14.1-r2.ebuild, + -files/pygtk-2.14.1-fix-numpy-warning.patch, + -files/pygtk-2.14.1-gtktoggle.patch, -files/pygtk-2.14.1-ltihooks.patch, + -files/pygtk-2.14.1-numpy.patch, +pygtk-2.17.0.ebuild: + Version bump, closes #328713. Load of bug fixes, closes #301658. Clean up + old revisions. Thanks for reporting.
