akhiezer wrote: >> From: Bruce Dubbs <bruce.du...@gmail.com> >>> Might it be best addressed in blfs chapter 2 or 3, if it's considered to >>> be a 'global', 'overview' kind of issue? BLFS users are ~expected to have >>> processed those chapters. That would help avoid a lot of repetition >>> elsewhere? >> >> From a practical matter, those sections will be skipped by a lot of >> users. Adding the preface matter as a prereq to a couple of packages >> seems to be the minimal solution. >>
> Your argument seems to say, don't put (presumably-deemed-)important info > like this into chapters 2 or 3, as "those sections will be skipped by a lot > of users". That would seem to be somewhat at odds with e.g. chapter-2 > being titled 'Important Information'. > > > Is there anything in those chapters - "2. Important Information", and > ch-3 - that should be moved to elsewhere, since from what you say "those > sections will be skipped by a lot of users", while at the same time it's > (currently) deemed important info. Judging from LFS, many people skip things like the preface. I don't know how many times users have run into problems because they didn't read the preface and run the host requirements script. Additionally, BLFS is designed to pick and choose. There are many who may have read the introductory chapters a long time ago and don't go back and reread them to get additional information when building something later. In C++, the general approach to defining local variables is to do it close to where they are needed. I think the same principle applies to BLFS. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
