> > I'd suggest you read what glib provides to get a clue WHY is is a > > requirement. "The GLib package contains a low-level libraries > > useful for providing data structure handling for C, portability > > wrappers and interfaces for such runtime functionality as an event > > loop, threads, dynamic loading and an object system." That's not > > the sort of stuff that could be optional. > > > By that logic, Glib should be required for every package in existence. > Yet, plenty of packages in BLFS alone can certainly compile and run > fine without it.
No, not at all. Some projects may not need or choose to use glib. What it shows, however, is that when it is chosen then it's used down at low- level code, not some runtime utility, like say font or image rendering. -- Paul Rogers [email protected] Rogers' Second Law: "Everything you do communicates." (I do not personally endorse any additions after this line. TANSTAAFL :-) -- http://www.fastmail.com - Choose from over 50 domains or use your own -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
