Matthew Burgess wrote: > On 27/09/2011 22:35, Ken Moffat wrote: > >> With respect, Matt, it's the glib2 part that is bloat. I remember >> some discussion, but I forget why we did it > > pkg-config upstream, as of 0.26, removed the internal Glib-1 that it > used to bundle, therefore forcing us to install a system-wide copy and > all of its dependencies. Now, if Glib had a modular configuration, and > if pkg-config documented which modules it needed, and if those modules > didn't need pcre/libffi/python, then that would be wonderful; we could > just install the subset of Glib2 we require, and advise folks to install > the full Glib2 package in BLFS. > > This is frustrating. As you say, it's Glib that's causing the bloat, > and ultimately, what pkg-config provides is useful functionality for a > base system.
You have to understand what glib is. It provides data structures for C for things like lists and vectors. If pkg-config was just written in C++, it could just take advantage of the Standard Template Library (STL) structures and do the same thing without the requirement for external libraries. Since the only thing in LFS that requires pkg-config is E2fsprogs, the easiest thing would be to patch the E2fsprogs build mechanism to remove the dependency on pkg-config and then remove PCRE, Glib, and Pkg-config and defer them to BLFS. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
