On Thu, Dec 11, 2003 at 01:00:34PM +0100, [EMAIL PROTECTED] wrote:
> > > I find the fact that we would need to break apart packages a bit
> > > annoying (and potentially a burden for releases and etc).
> > 
> > That would seem to be a problem. It is a fairly arbitrary 
> > imposition, so an unnecessary use (waste) of time in the longer term.
> 
> I've explained the reasons at length. But to summarise: We don't put
> unstable stuff in the GNOME Platform so we won't put unstable stuff in the
> GNOME Platform Bindings. And we won't put stuff in the GNOME Platform
> Bindings if it isn't a binding for the GNOME Platform.

Help me out here: 

    - Does GTK+ constitute a part of the GNOME Platform? If so, then I
      assume PyGTK would constitute a part of the Platform Bindings.

    - What does "stable" mean? None of the code AFAIK is under heavy
      development, so if the only criteria for splitting packages is not
      being "in-development" [which is a bit bogus] then 

    - Is there a requirement of completeness? Must the bindings cover a
      certain minimum percentage of the original platform library?

    - As a summarizing statement, how strict are we going to be towards
      package splits? Do you forsee PyGTK shipping more than two
      packages (pygtk and gnome-python) as part of the bindings?

> > My main disappointment in the "proposal" at the moment is 
> > that whilst it should still be in proposal status it is being 
> > pitched like a done deal.
> 
> I have given everybody time to respond, and received the explicit blessing
> of the GNOME Board and release team, but we can't wait forever. The schedule

Why was it not announced here earlier? 

> must start and releases must be made. I have given pygtk extra time by
> creating a December 22nd deadline for tarball submissions.

Yes, it gives us just enough time to package the tarballs and fill the
stockings with bug reports <wink>

Take care,
--
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 261 2331
_______________________________________________
pygtk mailing list   [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/

Reply via email to