On Tue, 15 Dec 2015 12:50:04 +0000 "Read, James C" <[email protected]> wrote:
> I'm writing with a suggestion for development of the latest current stable > LFS book. Version 7.8 at the time of writing. > > > I believe the addition of some simple custom unit tests at each stage in the > build process could serve a double purpose a) educational b) prevention of > error detection only later on in the build process I'm posting to the first post after reading the whole thread. I think it is overkill. This is what I see: Take all of the last 4 or so years of common issues. Mostly it is because people: 1) Don't remove build and source directories 2) Have dash as default shelel 3) Deviate from the book It's always been like that, and these extra commands to test the user is doing things right is ridiculous. The book commands work. I know people want to troubleshoot when they go against the book or a distro does something strange, but this is becoming ridiculous. The most common is people don't remove the build and source directories and too many people want to extract all of the source in one swoop and use it over and over with out cleaning. So, I suggest this: In each gcc, glibc, or binutils pass, test if bintuils or gcc build directories exist. And you may include gcc glibc or binutils build directories. Since people can't read and comprehend section 5.3, this is why we would need to include these security measures. There's no need to test variables because the user should be using the build nevironment. Okay so may as well test for that because lots of people think there are problems and use root. A whole can of open worms. For every page may as well add a check to see if they are using the LFS user. It's a pain, yes. But that's why support exists. But then, lots don't read the the FAQ. Mostly people don't read and comprehend. That's the issue. The current toolchain checks are okay, except for when people don't remove build and source directories. That's easily resolved. As developers, build what people commonly miss, record the issues,and build test upon that. If someone doesn't remove build directories, what is the outcome? That's what should be in the book, a test for that. Sincerely, WIlliam Harrington -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
