Randy McMurchy schrieb: > More than anything it would set a dangerous precedent if we started > including information about what could happen if you don't follow > the book. To me, that would stimulate a never-ending cycle of "well > I did this, and it didn't work, so could you add this to the book?". > > Just my thoughts on the subject. >
seconded. i use (b)lfs and the hints now for quite some time. in the beginning i just did as the book requests. meanwhile i've changed some build scripts and thus know that any, even the smalest, change can mess up the complete build. i suggest to write hints whenever a build-script has to be changed to be able to build another (yet undocumented) package depending on it. starting to add failure reports to the base will imho make the book unreadable as there are to many possibilities to mess up the build. i really like the book. whenever the build failed it was me i had to blame because i changed something. to much options will make the book unusable for a beginner, and a pro should be able to track what change broke the build. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
