1. Allow building without gtk-doc.
2. Run "configure" manually instead of let autogen.sh run it. It's
because autogen.sh sets CFLAGS, producing binaries with optimization
off and debug on. More seriously, the debug feature it uses
(sanitizer) is not suitable for a release build per GCC security
policy.
3. Add a link to the external dependency libdbusmenu.
DB is slated for remove in BLFS 12.1, so switch from it now.
Though postfix supports various DB formats, the only formats can be used
for postmap are btree, cdb, dbm, hash, lmdb, and sdbm. btree and hash
needs db; cdb, dbm, sdbm needs something out of BLFS. So lmdb should be
recommended or we'll have no postmap support.
This module fails to build on i686 due to an issue with the bundled
version of the PhysX SDK.
Since we're already disabling Qt3D due to a problem with the bundled
copy of assimp, let's just skip the Qt Quick bindings as well.
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.
- Make some grammar improvements to the description
- Use &qt5-deps instead of just Qt5, since this package uses qt5-base.
This package will build with the alternate version as well
The problem is that qt6 is not strictly required, qince qt5 can
be used. But an option has to be added for using qt5. Furthermore,
we have an established layout of describing options in a "Command
explanations" paragraph. So:
- Move qt5 to optional
- Add a note telling that qt6 is not strictly required referring
to command explanations.
- Add the said command explanation
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.
