Am Dienstag, den 18.09.2018, 21:34 -0500 schrieb Bruce Dubbs via blfs-dev:
> I've been working on a new book:
>
> http://www.linuxfromscratch.org/~bdubbs/basic-blfs-book/
>
> The intention is to be an intermediate book between LFS and BLFS that is
> much shorter and ease new users into BLFS and provide guidance into what
> packages are useful when initially building a system.
Great stuff!
> There are only six chapters in this book. I've spent some time trying
> to get the first two set up, but the others definitely need work.
Just a subject for disussion: The structure of BLFS groups the packages by type,
meaning grouping servers together, libraries to libraries, cmdline tools to
tools and so on. Looking at the huge amount of packages in BLFS, it makes
totally sence that way. I'm thinking about to break up that structure in
BLFS-Basic and do it like we did in LFS in which we build each package in the
order they are needed by subsequently built packages. In LFS, we do not have to
document dependencies as the build order resolves them implicitly.
What if we would do it in BLFS-Basic that way? For a newby it would be easy
to start as the entry point is quite clear: its the first package in book.
For an example:
which
popt
pcre
make-ca (regardless whether its a runtime dep for wget)
wget
...
Maybe grouping could be in parts like
"1) Widely used basic packages"
which
pcre
popt
libidn{,2}
libunistring
berkeley-db
make-ca
...
"2) Usefull command line tools"
gpm
sudo
rsync
wget
links
openssh
bind-utils
...
"3) Daemons"
postfix
fcron
...
I know that there are decisions to be made like "pam or not pam" but maybe a
comment can be added like "If you do not want PAM installed, skip this page
and the following 'shadow' page and continue with package XYZ." but for a newby
i think it makes live easier if pam/shadow comes textually before openssh which
optionally makes use of pam if installed.
> What I've tried to do is pull packages directly from BLFS, but there is
> an XML problem when the BLFS page has internal cross references that are
> not in the new book. This shows up mostly, but not entirely in the
> optional dependencies sections. What I've done so far is either just
> commenting these references out or converting them to external
> references. I do not see this ever being merged back into the main book
> like we did for systemd.
> One new approach I am making is to present both the System V and systemd
> sections on those few pages where there are differences. Users should
> be able to uses this book regardless of which version of LFS they
> started with.
>
> I am requesting feedback. No comment is too trivial. Spelling,
> punctuation, grammar, word choice, missing concepts, presentation order,
> missing or too many packages, etc are all fair game.
"Python Mpdules"
> I will note that the xml is a mess and needs to cleaned up, but right
> now I am considering this as a proof of concept.
>
> If you want to build the book yourself, the instructions I recommend are:
>
> svn co svn://svn.linuxfromscratch.org/BLFS/branches/basic blfs-basic
> cd blfs-basic
> make
>
> The output by default goes to ~/public_html/basic-blfs-book/
>
> All feedback is appreciated.
--
Thomas
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
