Jeremy Huntwork wrote:
I don't know. If we don't insert it in the book, what's the reason?
Because we're trying to keep LFS simple? Pfft. LFS by nature isn't
simple. I doubt Gerard started the project because he wanted to keep his
personal desktop 'simple'. Uncluttered and clean and minimal, yes, but
the process itself is by no means simple.
Quite frankly, from the comments I've been reading, most of those who
are opposed to putting this type of info in the book aren't giving
technical reasons. They simply say 'it doesn't belong there, it belongs
in a hint.' And that sounds more like they're just not interested in
change, or progression.
A large part of the way the book is written in the first place doesn't
have anything to do with technical issues - part of the reason for it is
to teach people how to build a Linux system and how it works. I'm
undecided myself whether adding this stuff to the book helps in that
respect, but just because it's not a technical reason doesn't mean you
can just dismiss it
Something like DESTDIR could be added, but stating that it's optional.
Perhaps the package installation instructions could just stay the same,
and a note could be added at the beginning of the book stating that it's
good sysadmin practice to know what's installed and describing what
needs to be done to check what "make install" does (and for any package
that doesn't follow the standard instructions just add a note to that
package "This package is non-standard. If you would like to check on
this package's installation procedure you need to [...]"
Of course the question is "what is the goal of LFS?". If it is just to
teach how to build a minimal, working system, then this suggested
addition isn't necessary - why does LFS need to worry about how users
use the system once it's built? There are plenty of books on sysadmin
topics...
--
JH
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
