This is stupid and it will cause meaningless diffs in version control
(like this commit does :( ).
Remove the kernel version from the generated XML files. Add
kernel.version file into git to track the kernel version.
I don't know these FS very well so I did not change things, except:
- "SCSI_LOW_LEVEL" should be "SCSI_LOWLEVEL" (without the "_" between
"LOW" and "LEVEL").
- RAID append mode is deprecated, so I removed it.
And I've fixed some issues in kernel-config.py as well.
clarify the rationale of the package and kernel support.
Note that we actually do not need this package if we only need to mount
FAT fs, not create or check or relabel it.
The issue is a new regression in 0.25.0, and it's causing test failures
in glib-networking and libsoup.
We know we are on Linux so we don't need the fancy #ifdef stuff, so we
can simplify the change into a sed.
I'm pretty sure it's at least not "required": there are some
configurations running qemu "headless".
And it seems qemu does not refers to any X components directly. It uses
X through SDL or GTK3, and they are already in the dependencies.
The instruction was a part of archived xf86-video-{amdgpu,radeon} kernel
configuration section.
Remove the kernel configurations from AMDGPU and Radeon because they
really should belong to the Mesa page or Xorg Server page.
Also create an ENTITY for qt5 or qt5-alternate and use that
to specify the qt5 dependenies.
The complete KF5/plasma packages should use the full qt5 build, but
the lxqt kf5/plasma components only need qt5-alternate.
It's not really QEMU specific.
By the way, move the "additional cfg unneeded on most systems" into the
bottom of the page, and adjust it to refer modesetting driver instead of
radeon driver.
Attention - you must have libxcrypt for this. If you are running an old
LFS release, install libxcrypt, then rebuild Shadow --with-yescrypt.
Technically if Shadow is built with PAM, then --with-{b,yes}crypt
switches are not necessary (but also do no harm). Just keep it there to
sync with LFS and prevent people building Shadow w/o PAM being locked
out of their system.
Well, my script did not handle package names with dashes correctly. So
some User Note links were mistakely removed. Recheck removed links
containing dashes and add them back if applicable.
