On Thu, 14 Oct 2004, Gustavo J. A. M. Carneiro wrote: > Qui, 2004-10-14 �s 08:31 -0500, Jon Nelson escreveu: > > On Thu, 14 Oct 2004, Gustavo J. A. M. Carneiro wrote: > > > > > Qua, 2004-10-13 �s 08:50 -0400, Chris Lambacher escreveu: > > > > Allong the same lines: > > > > Some things in gnome work on win32 and some do not. It will be easier > > > > to separate out the parts that work on win32 and the parts that do > > > > not. > > > > > > Every module in gnome-python is optional. You should be able to just > > > run configure and let it detect which modules to build based on > > > > That sounds great from a user's point of view (not), but from a > > developer's or packager's point of view you pretty much /always/ want to > > control what is and isn't included. Just because you have libfoo > > doesn't necessarily mean you want the program or library you are > > building to have libfoo support. > > If we added a configure option: > > --with-modules=gnomeprint,gnomeprint.ui,bonobo,... > > that problem would disappear, right?
Maybe but not necessarily. Let's say that gnomeprint *and* bonobo optionally depend on a library. Let's say that gnomeprint's use of that library is fine, but bonobo's causes crashes. What do you do then? Large unwieldy packages rarely make maintainers happy. It's not about finding solutions to potential problems and then saying, "We can do it this way because there are no more unsolved problems.", but rather a more philosophical point about whether or not it's appropriate to have one big packages or a number of smaller ones. One of the things I hate about QT is that it's one, HUGE library. If three changse are made to three different systems between release A and release B, there is no reasonable way to get only the changes you want, especially if those changes are broken, incompatible, or undesireable. In my opinion the whole point of having seperate libraries should be mirrored in having seperate bindings, or at the very least seperate source packages. It's not unreasonable to have some common code shared. Let me ask this instead: instead of asking why split them up, let me ask what the advantages are to having one uber-package? -- "Never try to write to ROM - it wastes your time and annoys the ROM." Jon Nelson <[EMAIL PROTECTED]> C and Python Code Gardener _______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
