These thoughts are prompted by my initial view of the kf5 additions. I don't enjoy building multiple packages on one page - in the case of kf5 the explanation of the wget options is educational, and the while loop with its use of $packagedir is also educational [ provided the directory always matches exactly the tarball name ].
But ... 1. I dislike not being able to see what each package does, and what uses it - I have never built the whole of BLFS, and I loathe wasting build time, and space, on packages which I will not need. 2. It is always nice to be able to find programs and libraries in longindex. For multiple-package pages this is possible, but without the package version, whereas on separate pages we can immediately see the package name and version.¹ For Xorg, the current layout is derived from the introduction of modular Xorg (from memory, 6.8 and 6.9 were released at the same time - 6.8 was monolithic, 6.9 began the use of separate packages) and at that time it offered a way of comparing the two builds to ensure they had the same result. Putting a new DE into the book is a majot job. I have no objection to using the "many packages on one page" approach as an initial step, but I hope that the aim will be to have one page per package (compare the systemd book's treatment of "kde5"). ĸen [1] - this requires people to add the indexing, of course, and it is the least-urgent part of adding a new environment. -- This one goes up to eleven! -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
