On Sun, 2004-03-07 at 19:02, Murray Cumming wrote:
> On Fri, 2004-03-05 at 16:14, Christian Robottom Reis wrote:
> > Hey there,
> >
> > We're providing a new PyGTK release candidate for testing:
> >
> > http://www.gnome.org/~jdahlin/pygtk-2.2.0-RC1.tar.gz
>
> That's great. Well done, and I hope this means you'll try to put pygtk
> on the GNOME Platform Bindings 2.7/2.8 schedule.
I'd love to see pygtk and gnome-python in the language bindings release
set, and was interested in finding out exactly what the issues are. As a
result I was talking with Murray and Christian (independently) on IRC
the other night, and suspect that the situation isn't quite as black and
white as it may have seemed (to me, at least). As I understand it this
is the situation:
- We all want to see Python bindings in the release set.
- Splitting packages that only wrap modules that are part of the
GNOME Developer platform [1] is NOT a requirement, if those
bindings are ABI/API stable.
- pygtk doesn't wrap any packages that aren't in the Developer
platform and would therefore not require structural changes in order
to be included.
- gnome-python does wrap packages that aren't in the Developer
platform, and is consequently not (currently) suitable.
As Murray put it, the bottom line is "don't break already-installed
applications". That's where the limitation on backwards compatible API
changes (and bindings for just the Developer platform packages) comes
from. So you can add API in unstable 2.5.x, but not in stable 2.6.1 or
2.6.2, etc. But after 2.6.0 you would be working on unstable 2.7/2.8
anyway and new API can go in there.
I'm not that familiar with the pygtk/gnome-python code, and it's not for
me to judge how easy any of the following would be to do (and I
appreciate that a lack of available resource limits our options).
Apologies if this is going over old ground, but it seems to me that the
following are possible ways forward:
- Do nothing.
- Work towards including pygtk in the GNOME 2.7/2.8 release schedule,
leaving gnome-python packaging as it is, just not included in
the release set.
- Include pygtk in the 2.7/2.8 release schedule, and split
gnome-python into two packages, one containing API stable Developer
platform bindings, the remaining bindings in the other.
I understand the reluctance to go for the third option (but would be
willing to have a crack at doing the donkey work behind the split myself
if time/resource was the main stumbling block).
Failing that, if there's enough interest in getting pygtk included in
the release set, what do people think of the second option?
Regards,
Graham
[1] http://www.gnome.org/start/2.5/modules/
_______________________________________________
pygtk mailing list [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
