Well, we generally do not like an update of "a part of the package",
esp. in this case we are doing an unversioned update. This makes the
book unstable, i.e. if a user executes this command a month after the
release of the book (s)he may get different results. And I don't think
it's a good idea to make vim &build-use-internet;.
And when we update vim to a new version (from 9.0.2103 to 9.0.2189 for
example), "make install" would already update the runtime files to
9.0.2189.
So just make the runtime update command nodump and move rsync to
optional.
This is a preparation for GRUB 2.12. With GRUB 2.12 EFI stub is the
recommended way to boot x86 (32-bit or 64-bit) kernels with UEFI, and
the old way is only kept as fallback.
Update to plasma-wayland-protocols-1.12.0.
Update to plasma5-5.27.10.
Update to kde gear-23.08.4 including kate, kwave, and falkon.
Update to kf5-5.113.0.
it is in instructions that are not guarded by role="nodump"...
Note that now that vim gets several updates a day, I am not sure
we use the right way to update runtime files!
In Linux 6.6, we can select DRM_FBDEV_EMULATION without FB, so FB is no
longer needed. And now FRAMEBUFFER_CONSOLE is not enforced (even if FB
is selected), so we need to select it manually.
Intel and AMD microcode support is now always enabled on x86[_64] and
CONFIG_MICROCODE is now hidden, thus remove amd-ucode and intel-ucode
kernel configuration info.
The other changes seem trivial.
The shipped configuration does not work at all on BLFS, so these files
are completely useless.
We were installing the files then overwriting them, but preventing the
installation can make our life easier when we reinstall/upgrade shadow
(then we don't need to recreate our BLFS-specific configuration).
The shadow installation procedure overwrites many files in /etc/pam.d/
which will render system login and su commands (among others) inoperative.
This update adds a warning at the beginning of the build instructions
so it will be hard to miss.
