On Sun, Jun 03, 2012 at 11:42:41PM +0100, Andrew Benton wrote:
> On Sun, 03 Jun 2012 22:36:41 +0100
> Ken Moffat <[email protected]> wrote:
>
> > Unfortunately, some of these packages may be broken
> > now that the pkg-config we are using does not require a full install
> > of glib2.
>
> It seems to me that with Pkg-config in LFS we can change some packages
> so that they now list Glib2 as a dep but there will be other packages
> that don't need Glib. The only way to know for sure is to do a test
> build on a raw LFS system which now includes Pkg-config :/ It's a lot
> of work that's easiest to do when updating a package.
>
> So what's the plan? Should we work our way through the book looking at
> <xref linkend="pkgconfig"/>s either change them to
> <xref linkend="glib"/> or just remove them? What about people with an
> LFS 7.1 system that doesn't have Pkg-config? Should we put a note on
> every page we change saying that LFS 7.1 users will need to install
> Pkg-config?
>
> Andy
At the moment, I'm hoping *most* of these packages need glib2. But
I've long believed that everyone who uses the svn version of the
book should be reading -dev, so they'll know about the possible
breakage :) [ cue hollow laughter ]
I'm still more interested in fixing systemd for udev-only, despite
your willingness to do without udev. So, I'm mostly relying on
*users* to flag breakage. Maybe I should note that on -support when
I update pkg-config and popt. Seems worth doing.
To be honest, people using gtk{2,3} will encounter the need to build
glib2 fairly soo after they've built xorg. It's less-used builds
(perhaps kde) that will take longer to identify b0rken dependencies.
ĸen
--
das eine Mal als Tragödie, das andere Mal als Farce
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
