The book presents a top layer in alphabetical order, with dependencies underneath. So our job is made much more tedious and difficult, hand (re)making the dependency trees to see which are lowest-level to be made first. May I suggest that if the book order were from lowest level first, installation order, it would be much easier for us, and eliminate an error-prone process everybody has to go through separately.
Yes, I know the counter argument is somebody might not have to or want to install all of them. How would they know that a-priori? I come to this section with the assumption that if it's in the book that alone is sufficient reason to install everything there--something or other I may not discover until later will want me to have installed something here. I might as well do it now along with everything else. Failing that argument being persuasive, does anybody here HAVE a list of the modules in the proper installation dependency order they could contribute to me? I'd be ever so grateful. TIA -- 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 - A fast, anti-spam email service. -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
