Ken Moffat wrote:
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.
You can always choose what to (not) build by just commenting out the
packages you do not want. I'll note that we also build a lot of things
we may not need in packages like KDE4's kdelibs and Qt.
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.ยน
The way upstream is releasing KF5, all the packages have the same 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").
I do not want to do that for two reasons. First, very few people will
want to go through the packages one by one. Second, updating (IIRC) 68
pages with every release is more work than editors really want to do.
In other words, the effort is not worth the benefit.
[1] - this requires people to add the indexing, of course, and it is
the least-urgent part of adding a new environment.
It would be nice to get a volunteer to do that. Even with the systemd
example, it was a non-trivial exercise to get it into the book. There
are other pages that can use descriptions too.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
