akhiezer wrote:
Date: Mon, 25 Jan 2016 09:20:48 +0000
From: [email protected] (akhiezer)
To: LFS Developers Mailinglist <[email protected]>
Subject: Re: [lfs-dev] Change proposal - move external build directories -
part 2
.
.
As for assisting users: maybe it is now time to put such commands into each
(relevant pkg-compile) page explicitly; use xml/&c template inclusion,
overridden in non-default cases - usual stuff.
Of course, one view is that one wants to 'factor out' such common parts,
as much as possible from the individual pages of the book.
To help avoid the most-commonly-arising issues - mainly those from new-users
- would it be useful to introduce a 'test' page, early in chapter 5
(for example; &/or elsewhere are wanted), that verifies automatically
that the user is doing properly things described before - such as: is
using bash; got $LFS set ok; can do mkdir/rmdir of a package build-area;
is copy'n'pasting backslash-line-continuation ok; & any other such issues
that arise commonly on the mailing lists &c.
The idea is basically to introduce a small-ish 'test suite' of commands -
or compound command(s) - that can be copy'n'pasted in more-or-less one go;
and will fail in a readily-pinpointable manner, if any of said requirements
are not being met properly. That could help alert further - and with a
practical example - the user very early in their build, to the kind of
basic pitfalls that they need to avoid, in order to achieve a successful
build.
The intent is to, not 'nanny' or hand-hold unduly, but instead to address
the concrete, known issues that, as said, arise commonly; although their
frequency is perhaps not quantified, they are at least known qualitatively
to many that follow the lists &c.
I'm thinking about writing a "Frequently Made Errors" page. It wouldn't
go in the book, but be more like a hint. The book could reference it though.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
