For some reason, the stylesheets generate a
<div xmlns:xlink="http://www.w3.org/1999/xlink" ...> element in
longindex.html, but this is not valid in xhtml (the attribute
xmlns=xlink is not defined in the DTD). The problem is that tidy then
thinks it is not a true xhtml and removes the doctype declaration.
But when a browser receives a file without doctype declaration, it
thinks it uses an old standard, and switches to "quirks mode"
(for firefox, this can be seen by typing ctrl-I on the page).
- according to our typography, referring to a manual page should be
<filename>page(x)</filename>
- don't enclose punctuation into quotes
- use <option> for option
Since it is needed for both building and installing, exporting it
allows to have it defined even if building as a regular user (so that
sudo is run for installing) or using a package manager (which usually
runs in a new shell and forgets unexported variables)
- Update to meson-1.3.1 (#5402)
- Update to vim-9.0.2189 (#4500)
- Update to inetutils-2.5 (#5404)
- Update to xml-parser-2.47 (#5403)
- Update to linux-6.6.8 (#5397)
- Update to tzdata-2023d (#5399)
- Update to setuptools-69.0.3 (#5400)
- Update to iana-etc-20231205 (#5006)
- Update to autoconf-2.72 (#5398)
- Update to grub-2.12 (#5396)
In Linux 6.6 DRM_FBDEV_EMULATION no longer depends on FB, so we no
longer need to select FB (tested in a QEMU VM).
But if DRM is selected, we must select both DRM_FBDEV_EMULATION and
FRAMEBUFFER_CONSOLE or we'll see only blank screen. And now
FRAMEBUFFER_CONSOLE is not selected by default, be warned!!
I don't see a reason to upload vim tarball onto anduin. And now anduin
does not have vim-9.0.2136.tar.gz.
I tried downloading vim-8.0.0586 (shipped by LFS 8.2) from GitHub and it
worked fine. So it seems the GitHub storage is stable enough.
Update to vim-9.0.2136.
Update to iana-etc-20231117.
Update to bc-6.7.3.
Update to wheel-0.42.0 (Python Module).
Update to perl-5.38.2.
Update to pkgconf-2.1.0.
Update to readline patches 002 through 007.
Update to openssl-3.2.0.
Update to setuptools-69.0.2.
Update to linux-6.6.3.
Update to meson-1.3.0.
This is more consistent, and it reduces the number of different
translatable strings for translators. Most of the package names in
whatsnew has already been aligned with <title>s, now make these two
"from ..." packages so.
When /dev/shm is a symlink we need to create its target or some tests
will fail and Python 3 will be misconfigured. We wrote it as:
mkdir -pv $LFS/$(readlink $LFS/dev/shm)
But if $LFS/dev/shm is a relative symlink (say ../run/shm), we end up:
mkdir -pv /mnt/lfs/../run/shm
This command will create /mnt/run/shm, not $LFS/mnt/shm as we expected.
Twist it a little to make it work for both absolute symlinks and
relative symlinks.
