Am Dienstag, den 11.09.2018, 15:30 -0500 schrieb Bruce Dubbs via blfs-
dev:
> 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.
>
> The first is easiest, but would probably not be used much.
>
> The second is an intermediate approach that is basically adding a
> single
> web page to the book.
>
> The third could be done with symbolic links within the xml sources
> to
> existing pages, but would be experimental.
>
> In creating the list below, I went through the table of contents of
> BLFS
> to decide what I'd recommend most users need. I then looked at each
> package's required and recommended dependencies.
>
> I feel that most users will want a workstation of sorts, but some
> packages suggested would not be needed for a sever (e.g. Xorg, dhcp,
> wireless).
>
> In the list, dependencies are indented and would need to be built
> first.
> For example in the security packages
>
> Security
> make-ca-0.9
> p11-kit
> libtasn1
> six (perl module)
> openssh-7.8p1
> sudo-1.8.25
>
> p11-kit, libtasn1, and six need to be built before make-ca but those
> packages do not need and dependencies themselves. The others can be
> built without any dependent packages.
>
> Of course Xorg is by far the most complex. There are several levels
> of
> dependencies there. This list could be reordered into a linear list.
>
> What I'd like to do is to start a conversation about whether this is
> worthwhile and if so, what is the best approach. I also would like
> to
> discuss whether my list has everything it needs (or if there is
> something not needed.)
>
> Thanks.
>
> -- Bruce
> ===================
> BLFS Basic Packages
>
> Configuration
> The Bash Shell Startup Files
> The /etc/vimrc and ~/.vimrc Files
>
> Security
> make-ca-0.9
> p11-kit
> libtasn1
> six (perl module)
> openssh-7.8p1
> sudo-1.8.25
>
> Disk Management
> parted-3.2 (for partprobe)
> LVM2
>
> General Utilities
> lsof-4.91
> libtirpc
>
> System Utilities
> cpio-2.12 (for building initrd)
> fcron-3.2.1
> gpm-1.20.7
> hdparm-9.56
> logrotate-3.14.0
> popt
> pciutils-3.6.2
> unzip-6.0
> usbutils-010
> libusb-1.0.22
> Python-2.7.15
> which-2.21
>
> Networking
> dhcpcd-7.0.8
> net-tools-cvs_20101030
> ntp-4.2.8p12
> LWP::Protocol::https-6.07 (Perl Module)
> rsync-3.1.3
> popt-1.16 (also for logrotate above)
> wget-1.19.5
> make-ca-0.9 (listed above)
> wireless tools-29
> wpa_supplicant-2.6
> libnl-3.4.0
> bind utilities-9.13.2
> traceroute-2.1.0
> links-2.17
> mailx-12.5
>
> Servers
> postfix-3.3.1
> Berkeley DB-5.3.28
> libnsl-1.2.0
> rpcsvc-proto-1.4
> libtirpc-1.1.4 (listed above)
>
> Graphics
> xorg-7
> fontconfig-2.13.1
> freetype-2.9.1
> libpng-1.6.35
> which-2.21 (listed above)
> harfbuzz-1.8.8
> icu-62.1
> glib-2.58.0
> pcre-8.42
> libxslt-1.1.32
> docbook-xml-4.5
> docbook-xsl-1.79.2
> sgml-common-0.6.3
> libxml2-2.9.8
> UnZip-6.0 (listed above)
> libdrm-2.4.94
> Mako-1.0.4 (Perl module)
> Beaker-1.10.0
> funcsigs-1.0.2
> MarkupSafe-1.0
> Python-2.7.15
> libvdpau-1.1.1
> wayland-protocols-1.15
> libxml2-2.9.8 (see above)
> LLVM-6.0.1 (only required for Gallium3D, r300, and radeonsi
> drivers and for the llvmpipe software rasterizer.)
> Pixman-0.34.0
> libepoxy-1.5.2
> mtdev-1.1.5
> (Appropriate drivers for HW)
>
> fluxbox-1.3.7
I like the idea of building a separate book. All the "infrastructure"
to do so is allready there, so the setup shouldn't be that
complicated. It might also have the advantage that there are relativly
few packages in it. When a release comes up, those packages should be
carefully verified on the -rc quite quick, even if there are more rc's
than just -rc1.
The remainder (the current book minus the basic-book) could be seen as
addons but might not be verified completely at a release of a new LFS-
book As editors, we should walk thru anyhow but it would reduce the
pressure and amount of work at release time and the verification could
be an ongoing process independently of a release. This accepts
potential breakage if there are incompatibilities between a new release
and a BLFS-addons-package, but it would not be required to have it
fixed before a release.
A hint might be something that is created easily but hardly used as i
assume most of LFS users either use jhalfs or has own tools to build
command files from books source. Support by jhalfs shouldn't be dropped
and if so, that might be one reason why a hint doesn't get used very
intensive.
An additional page in the existing book would not bring the advantage
of the new book, just another page to maintain.
Here my list of packages i immediately add to a new LFS build (sorted
by dependency):
which pcre popt gpm ed db(=berkeley-db) libtirpc rpcsvc-proto
libnsl pam shadow sudo openssh libidn libunistring libidn2
zip unzip libtasn1 nettle p11-kit gnutls ca-certs curl
wget rpcbind nfs-utils nfs-client dhcpcd libcap
io-socket-ssl ntp lynx netfs initd-tools
followed by tools for (B)LFS-editing/development and other system tools
nano sqlite python2 libxml2 libgpg-error libgcrypt
libxslt docbook-xml docbook-xsl sgml-common docbook-dsssl
apr apr-util serf swig subversion rsync apache
libuv p11-kit gnutls libarchive cmake tidy patchutils
run-parts fcron
and X11+xfce4
geany
I like xfce for being a (in my opinion) perfect balance between
easyness to build and the functionality of the DE - but fluxbox is for
sure even more easier to build.
I do not need disk/partition tools as everything i do is in virtual
machines (setup one time with one /boot, /home and swap partition plus
two system partitions where LFS resides on and build the next machine
on the other system partition.
cpio, lzo and mdadm(with a small patch) are part of my multilib-version
of the LFS-book. Some others (like patchutils, geany, run-parts) are
not in BLFS book.
--
Thomas
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
