Uh, glib isn't terribly heavyweight, you know. syslog-ng moved to using
glib some time ago (from its previous weird homerolled object system), and
y'know how many problems that caused that critical system daemon?
None, that's how many.
I'd understand your complaints if it was *gtk* being pulled in, but glib?
Even if you're not using a single glib-using app, the memory hit is at
most a few dozen pages of memory, in *total*, across every single
glib-using app. Are you so memory-starved that a few dozen pages is even
detectable?