Gerard Beekmans wrote: > Dan Nicholson wrote: >> So far, the votes are: >> Me: Move up libtool and grep, note about missing automake >> Chris: Same >> Jeremy: Add note about missing automake and libtool > > From the sounds of it, grep and libtool can be moved up the chain > without side effects. Let's go for it. Having less tests skipped due to > missing packages is a good thing. We still may not be able to run every > single test until autoconf's and automake's test suites are run again > further down chapter 6 when circular dependencies have been resolved. > > But then, autoconf and automake aren't all that critical to warrant a > second installation. > > As such I vote for moving up libtool and grep, then add a note at the > end of chapter 6 (or earlier, whenever all dependencies are finally > satisfied) to run the tests again "just in case."
My vote is to agree with Gerard. However, I think we need to reconsider the purposes of the test suites of individual packages. They are not really designed to check that a released version is built correctly. They are intended for developers that are changing code. If a change is made, then regression testing is essential. I don't think it is unreasonable to assume the developers have run all the tests with all the proper prerequisites in place before releasing a stable package. Our use of the test suites is a pleasant side effect to give us assurance that we built the package properly, but we shouldn't obsess about making sure that every conceivable regression test is run. Reordering packages is reasonable. With the exception of the toolchain, building packages multiple times where the only purpose is to get more test coverage is not. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
