On Thu, 2007-04-19 at 12:33 -0500, Brandon Casey wrote: > I am posting to suggest that glib has crossed a threshold > of size and functionality and that users would benefit from > a splitting of the library into two or more separate libraries. > > [...] > > The growth in size and in dependencies is making it difficult > to compile glib on non linux platforms. It is regrettable > that some software projects have to avoid glib because of this, > and then re-invent the wheel when glib has a well tested, stable > and secure version.
I think we need some specifics: - What exactly is not portable? - On which non-linux platforms is it failing? - What dependencies are problematic? - Which projects are known to be suffering as a result? While I agree that the GLib maintainers need to be prudent about what goes into GLib, almost all of what's currently in there seems like pretty basic stuff to me. I think the definition of "basic functionality" has expanded over time, though, and C needs more and more help to keep up with functionality that's implicit in other, more modern languages. Also consider the fact that GLib already consists of multiple libraries (GLib, GObject, GThread, and possibly a future GVFS). -- Hans Petter _______________________________________________ gtk-devel-list mailing list gtk-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-devel-list
