On Wed, Oct 13, 2004 at 10:41:21AM +0200, Murray Cumming wrote: > End "users" don't pick gnome-python packages - they pick applications and > sane distros do the rest for them. > > End "developers who use pygtk" don't use the source tarballs - they use > the distro packages, which are usually split up completely even if the > tarball isn't.
Ah, not everyone. Most distros take a while to package things, and because the rate of change lately has been quite fast, many important and valued people will use tarballs to ensure they have the latest code. We want to encourage them because it's very valuable QA to have them test packages before they hits distros. > 3. You would be able to release fixes for the gnome-vfs bindings, for > instance, even if the bonobo bindings, for instance, are temporarily > broken. Rate of release is normally not that fast, and we have a policy of avoiding breakage in CVS HEAD. There was a slight bending of that during the recent threading changes, but it's something I'd call exceptional and we'd probably just back out changes that weren't so controversial. > 5. It will be easier to share maintenance - in particular, different > people can decide when different parts of gnome-python make new releases. > The whole thing is a lot of code for one person to maintain. I don't know. I don't see a parade of maintainers vying for control of libgnomeprint, if you know what I mean. In particular, I don't think they'd be put off hacking on libgnomeprint just because it lived in pygtk-extras. I'm thinking about the other points, which are the really important ones. Take care, -- Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 3361 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/
