On Wed, Oct 23, 2019 at 08:46:06PM -0500, Trent wrote:
Is there any reason LFS does not include WGET?
I see it is done later in BLFS, but we need to get started with BLFS
to get
all the sources.
Trent
There are many packages which various people require to get a usable
system. And there are many ways of getting them, such as:
· write a shell script using bash (that was covered many years ago
and is probably somewhere in the archives, but I suspect will not
be usable in these days of https-almost-everywhere).
· build in chroot, using the host system to download and to read the
instructions
· read enough of BLFS to note what you need, including their
dependencies (and don't forget links or lynx if you need to read
the book) then download them, make notes on how to build, and
build them after booting.
In general, for a first time build (and despite your reports of
rebuilding several times, you are still on a first time build) I
suggest that you get LFS to boot, check that it works correctly,
then work out what you need. From that work out the dependencies,
and then build all things you regard as essentials for the minimal
system from chroot.
That should give you enough to then be able to boot the system and
use a tty to build and another tty in which you can read the book
and download other packages, with perhaps other ttys to monitor 'top'
and to write your notes.
And if you plan to build a desktop system running Xorg, you should
NOT regard Xorg as something which needs to be built before you boot
the system for a second time. Reading a text browser is the way to
go.
The best results are usually obtained by looking at alternatives (at
least, once you have a working Xorg and a working graphical browser)
and expecting some of your initial decisions about what to build,
and in what order, to turn out to not be ideal (e.g. building
packages which sound interesting, but turn out to not be to your
taste). Keep notes, then hopefully the second build will be better.
LFS is about learning, enjoy the process. And if you use scripts,
learn how *your* scripts can fail and take steps to stop the build
if that happens.
As an example, here are the packages I build at the start of my
"things to build before booting" script - there are many more (e.g.
git, links, nfs, postfix, things not in the book) and the
dependencies I build might not match your choice or your needs.
But please note that without the installed certificates wget will
only have limited use.
random bootscript (sysv, systemd updates this)
which (I use the bash script version)
sqlite (without looking, not sure if the items here need this)
libtasn1
p11-kit
make-ca
libunistring
libidn2
wget
ca-certs (I will reinstall certs later on desktop systems)
All I can say about the above is that their positions match my
current builds, both 9.0 and recent svn. Over time the positions of
things in the build change.
ĸen
