id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
962	Move Man-DB after Libpipeline	William Harrington	clfs-commits@…	"Martin brought up a good point of moving Man-DB right after Libpipeline. There is no need for it to be where it is right now in the build. LFS had it before vim and I put it before vim and had never moved it properly. The only reason it is like that in LFS, is because Man-DB needs to be after Util-linux for test suite coverage.

For CLFS, we don't have the issue of building Util-linux so late in the final-system build, so Man-DB can be right after Libpipeline and have full test suite coverage."	task	closed	trivial	CLFS Standard 3.0	BOOK	CLFS Standard GIT	fixed		berzerkula@… jonathan@…