On Wed, 2012-12-26 at 09:38 -0800, Paul Rogers wrote: > Certainly. I do have goals to get to. But a newbie would, I think, > benefit from being told that (s)he needs to build certain dependencies, > with PERHAPS some guidance to what a good set would be, before getting > to the goal of a functional desktop.
That doesn't make sense to me - dependencies are something you build because you need them, not some set of common packages you install because something else might need them. To take an example from some old notes I've just been re-reading, I wanted to try running systemd on LFS, instead of the traditional sysvinit. So I tried installing that, and found it depended on dbus, gperf, glib, etc. And so I went to install dbus, which depended on expat which didn't seem to have any dependencies. My point is, how else would I do this? I install expat only because dbus needs it, and from memory, it's the only thing that does. And I install dbus only because systemd needs it, though I know that other things will use it later. And in all of this, I don't see some common set of packages - just the things I want to install, and the other things I need in order to do so. Simon.
signature.asc
Description: This is a digitally signed message part
-- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
