On 09/11/2018 03:30 PM, Bruce Dubbs via blfs-dev wrote:
I've been working on a concept that I am calling BLFS Basic. This is
basically a subset of BLFS Packages that should be a part of most
systems after LFS. I will attach my list at the end of this post.
What I want to do is give new users an idea of what to build first to
flesh out their LFS systems into something usable.
There are several ways to go about this:
1. Write a hint
2. Add a chapter to BLFS with links to the appropriate packages.
3. Create another full book with the needed packages.
My vote is for #3 (regardless of responses to anything below). I haven't
authored a response with any comments on suggested content because I'm
not entirely sure I have a complete understanding of the goal. Following
is random thoughts, basically in order as I was trying to figure out my
excuse for lack of a response. :-)
My understanding is that #3 most closely matches the proposal as
originally outlined - which I begrudgingly supported at the time, but
eventually grew on me and I was quite happy to let it roll full steam
ahead as was. However, it now seems to me that this proposal has
changed, and is now some form of compromise with stripping the book
down, but only for the purpose of our semi-annual release date, where
the existing book would remain largely unchanged and continue as a
rolling release. Am I incorrect in my understanding?
If the above is at least somewhat correct, there is nothing preventing
us from building both books from the same source tree with a different
say "index-desktop.xml" instead of a top-level index.xml, a separate
chapter layout with nothing but a chapter.xml file with relative links
to the original pages, a single entity change for the pages that are
shared, and one additional file for entities on the shared pages. Does
that sound like a reasonable approach?
If the above is at least somewhat close (or even under consideration if
it wasn't before), then I don't see a need to be hard and fast about
what is included from the get go. I'd say just go with Bruce's list as
it is now for the initial POC, and we can tweak it as we go. I figure
each editor/contributor/end user who is following development should
actually use the end product in practice for a couple of weeks and see
what we install after that until it _feels_ complete to each individual.
We have ~ five months to hash it out.
Additionally, if something like the above is being considered, I see a
real potential for this to branch out a bit more than what was
originally intended, a more linear approach to a specific desktop
environment, or even a complete server appliance, but almost no
additional work beyond the initial inclusion of
index-{desktop,server,whatever}.xml...a build recipe of sorts.
Of course, the first is the most difficult, I understand that, seems
right up my alley if I did not already feel as if I were spread too
thin. While I'm sure it's not _quite_ as easy as I've made it sound
above, I see that the potential is there for just about anybody to
create a target specific book who's content is already 99%+ complete,
and leverage jhalfs to make repeatable builds from start to finish for
just about any project they have in mind.
--DJ
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
