On Wed, 2003-09-03 at 19:19, James Henstridge wrote: > On 3/09/2003 9:50 AM, Malcolm Tredinnick wrote: [...] > >What do you think about moving the gtksourceview bindings into the main > >module (I'm not sure where exactly in the directory tree)? This is all > >said without having talked to the maintainer about his plans, but I like > >the idea of having a single-source download for this kind of stuff. > >Things like vte are different, since it includes the Python bindings in > >the main module. > > > This is an interesting question. I really don't want to stick bindings > for too many libraries into the pygtk tarball. I think it is a good > thing that it is fairly low in the dependency stack, since it makes it > easier for other packages to depend on pygtk for their builds. > > Making these sort of things optional dependencies is really a copout > though. For people building packages (ie. Linux distros, etc), the > optional dependencies are essentially hard dependencies if they want all > features of the package to be built (even if they then split things up > into multiple binary packages). If pygtk has an optional dependency on > libfoo, then other packages that depend on pygtk (optional or not) will > also depend on libfoo. If these dependencies get too complex, they are > likely to either (a) not build pygtk's libfoo binding, or parts of other > packages that depend on pygtk.
I agree with all of this. My original mail may not have been too clear: I was asking about including it under the gnome-python CVS module, not inside pygtk itself. It is already beneficial to only need a stack that goes up to GTK+ to build PyGTK. > Now it might make sense to distribute the GtkSourceView binding with > gnome-python. Alternatively, it might make sense to package them with > GtkSourceView itself (like with VTE). I don't know. Obviously the latter makes the most sense. Rather than us all having a hearty round or two of "it would be nice...", I will follow this up with the various maintainers and see what falls out. Cheers, Malcolm _______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
