Some notes:
- proftpd has been supporting PCRE2 since 1.3.8a.
- bluefish actually invokes PCRE via Glib, so since Glib was ported
from PCRE1 to PCRE2 bluefish has been using PCRE2 in fact.
- zsh and rasqal will support PCRE2 in the next release. For zsh pcre
is not used with book instruction anyway, and for rasqal the
maintainer suggests just relying on Glibc regex.h before the next
release.
- The other distros (Fedora for eg) are already disabling PCRE for
slang.
For xarchiver we're already using GTK+-3, and we're getting rid of
GTK+-2 soon (GIMP3 has hit it's final developer release). This is one
less reference to worry about cleaning up later.
I've tested this and it seems to work as expected.
This should protect TigerVNC Server against all of the CVEs fixed in
xorg-server since xorg-server-21.1.6 was released.
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.
The is no /usr/lib/systemd on a sysV build so remove the instructions
in thunar and tumbler to remove /usr/lib/systemd/user/*.service.
Drop unused libglade dependency from xscreensaver.
I've marked most of these as 'role=nodep' so that jhalfs doesn't pick up
multiples in cases where it's not needed.
Transmission, Libreoffice, CMake, Poppler, and Appstream now have Qt6
ports working well.
I have left Qca, gpgme, polkit-qt, and other KDE-related packages alone.
They do have support for Qt6, but we should not list them as they are
incompatible with the Qt5 versions and we could end up causing
unintentional breakage by doing this.
Note that if you build something relying on $SHELL, it may still fail to
build in chroot.
In the chroot we first use "env -i" to clean the environment variables.
When bash starts with no $SHELL set, it *sets* SHELL=(the login shell
of current user specified in /etc/passwd), but it *does not export this
variable*.
For example:
$ cat > t.c << EOF
#include <stdio.h>
#include <stdlib.h>
int main() { puts (getenv ("SHELL") ?: "(nullptr)"); }
$ ./a.out
/bin/zsh/
$ cc t.c
$ env -i bash -c "echo $SHELL"
/bin/zsh
$ env -i bash -c "./a.out"
(nullptr)
We can remove this now only because Mozilla has added a workaround into
their building system at
https://hg.mozilla.org/mozilla-central/rev/5afe7b911f61 for some Mac
builder, inadvertently fixing our issue.
Link: https://lists.linuxfromscratch.org/sympa/arc/blfs-support/2014-11/msg00050.html
Link: https://lists.linuxfromscratch.org/sympa/arc/blfs-dev/2023-11/msg00136.html
If a newline is inside the comment, it won't be rendered. So we can
avoid an excessive amount of empty lines in seamonkey, and break the
long comments about RELR into multiple lines.
GTK+ was renamed to GTK in GTK 4, and WebKitGTK+ was renamed to WebKitGTK
correspondingly.
I've not touched the ChangeLog but we should avoid "+" in the future
ChangeLog entries.
Link: https://bugs.webkit.org/show_bug.cgi?id=264161
