neither firefox nor epiphany can download them, and they are not
well maintained, because rarely tested.
This is WIP because the "(HTTP)" part of "Download (HTTP)" will
need to be removed too.
But let's see what users think first...
It now unconditionally runs gtk-update-icon-cache (or
gtk4-update-icon-cache) after installing the icons. As a result, we need
something to install gtk-update-icon-cache.
For the benefit of jhalfs, I've set gtk3 as a normal dependency, but
gtk4 as a nodep :)
Thanks goes to Joe Locash for the report.
When the patch can be converted to a not-so-long sed, we prefer the sed
because it tells people "what this command is doing" more explicitly and
also reduces an additional download. And for patch or sed we need a
<para> describing "what it fixes".
It's also a bad idea to fold the patch/sed command just before "meson"
in the same <screen> because it'd be too easy to overread it.
It's optional for the packages that use it, and they only use it to
provide additional support for profiling.
Sysprof now requires two more packages which are specific to it, so
let's archive it.
- make change from /usr to opt/xorg "nodump"
- make the removal of "-nolisten tcp" "nodump"
- narrow the change from none to on to the "Numlock" line: otehrwise
the comments about this option become incomprehensible:
(e.g. "option can be on, off, or on")
If xmlto is not installed and -Dgtk_doc=false, there will be no
documentation installed.
Also add a rm -rf command so we won't do things wrong reinstalling the
package.
We recommend using the /usr prefix for xorg, but the instructins
for putting it in /opt/xorg do work. For jhalfs, having optional
instructions is confusing, so we mark the /opt/xorg "nodump" so
they will be ignored when automating BLFS.
I had the Intel Media Driver installed on this system at some point in
the distant past, and it installed /etc/profile.d/intel-media.sh - which
overrode the libva-intel-driver, and caused gstvaapi.so to fail to load
correctly on Wayland... which then caused GDM to fail to start. Note
that X11 worked fine because of using a different code path.
If we had the Xorg Drivers section still with xf86-video-nouveau there,
this probably would've gone over there originally, but this place fits
well.
The original plan was to put this into LFS, but I decided against it
since it works fine until you start using programs such as Epiphany or
KDE Plasma.
1. Remove redundant paragraph for Cantarell, left over from when it
was at gnome (latest gnome versions do not ship the fonts, only
the source - prepared TTF fonts are at Google fonts).
2. Reword the old KDE comment in Noto fonts, replace by mentioning
that Noto fonts are preferred for everything in KDE Plasma and
applications, except for monospace - and add link to Hack for that.
3. Comment Oxygen fonts.
I'm pretty sure most desktop apps can use variable fonts today (even
Xterm renders variable fonts fine). But there is indeed something not
working, notably xelatex.
PRC contains mainland China, Hong Kong, Macao, and Taiwan. (In some
uses "mainland" also contains Hong Kong and Macao, but it depends on
the context).
In mainland China many users want TC and JP fonts alongside SC font
because once you know SC you can just read TC seamlessly, and many
Chinese Linux users (not including me) are Japanese cartoon or game
fans. IMO using the monolithic CJK .ttc font file is easier.
1. mention variable fonts (not generally useful for the desktop)
2. Cantarell is now at google fonts
3. The organization of Noto fonts has changed. Provide an example
for how to download, and working links for the CJK variants (now
just Noto Sans JP etc).
4. Oxygen Sans and Mono now at google fonts, but each is separate.
5. Comment the Noto Sans CJK item, the links are no longer useful
and the fonts have been renamed.
6. Fix the debian UMing link to point to the tarball.
One of the things I've been doing over the past week is building
packages that list &qt5-deps or &qt5-components with Qt Alternate and Qt
Components.
For each one I've been checking logs for relevant information to Qt. It
doesn't show up in my logs, so I checked the Configure script and didn't
notice anything in there either.
When checking the NEWS file, I found out that several backends have been
removed - including cogl, qt, and DirectFB.
With Mesa-23, all of the tests other than the ES2 tests will fail due to
minor differences in behavior between Mesa-22 and Mesa-23.
This doesn't seem to cause any problems at runtime, so we'll just
document the failures.
If setxkbmap is not installed, Xwayland will refuse to start.
In a "normal" build Xorg applications should be pulled in by Xorg fonts
-> xcursor-themes -> Xorg applications, but we are saying "only
font-util" for Xorg fonts and font-util does not need xcursor-themes.
1. Don't throw unspecified entries too early. Doing so caused various
rendering glitches. And we can now also check if an entry is
selected but it's parent not.
2. "menu"s in Kconfig can also have dependencies...
Some pre-existing .toml data files are found problematic after the
change, fix them and regenerate all rendered -kernel.xml files.
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.
The kernel-config.py script takes a toml file containing a set of
kernel configuration key-value pairs. Then it parses the Kconfig files
in a kernel source tree and render the given configuration as a
LFS-style <screen> in a separate XML file. The XML file can be used in
the book with xinclude.
Some "features":
1. The lines are limited to 80 columns.
If the text of the configuration option is too long, it will be
trimmed; if the symbolic name of the option cannot fit in this line,
a separate line will be used for it.
2. If a configuration option is given but it does not exist in Kconfig
files, the script will abort immediately. This helps catching
removed options.
3. The script also aborts immediately if a configuration option is
illegal, for example setting an option to 'M' while it cannot be a
module.
4. The infrastructure is not wired into the main Makefile. It's because
not all editors have the latest kernel tree, and even if they do the
locations of the kernel tree are still different. To update the
generated XML files, use
"make -C kernel-config KERNEL_TREE=/sources/linux-x.y.z".
Backword incompatible change:
The script no longer outputs "CONFIG_" prefix for the symbolic name. It
really does not make too much sense to waste 7 characters here because
it's a common prefix for all options!
A limitation:
The script does not really validate the configuration. Generally
validating the configuration requires to solve the 3-CNF-SAT problem,
which is NP-complete.
1. Move the configuration file into /etc, to be consistent with other
configuration files created in BLFS.
2. We no longer need a separate "configure the graphic card" example
because the TearFree configuration file is already a good example.
3. Tearing issue is really not new after xf86-video-* removal. In some
xf86-video-* drivers a TearFree option is available but rarely
enabled by default (only the amdgpu driver when the output is rotated
or transformed). So this is actually the first time we document it
in BLFS.
4. It's really not difficult to observer the tearing by dragging a
window in twm, despite twm only renders the window border during
dragging.
With modesetting driver, $HOME/.local/share/xorg/Xorg.0.log contains:
[ 65817.713] (II) AIGLX: Loaded and initialized crocus
And there is no more "AIGLX error" messages.
I really don't understand what it is for. And I can run twm without it.
If someone has a good reason to use legacy fonts, please revert, but you
should at least consider marking it runtime and maybe demoting it to
optional.
Or any Qt5 app will complain:
qt.qpa.plugin: Could not find the Qt platform plugin "xcb" in ""
Let's recommended them. On Wayland-based DEs we can export
QT_QPA_PLATFORM=wayland to avoid depending on xcb though.
It looks like we've forgotten some dependencies for Qt5 all the time.
And many dependencies of Qt5 are also needed by the alternative. I
gathered them via
readelf -d $(find -name \*.so) | grep NEEDED | grep -o '\[.*\]' |
sort | uniq | grep -v Qt 2>/dev/null
in the Qt5 alternative build directory.
In the regex we use `|` which is extended regex. So the `-r` (or `-E`,
or `--regexp-exteneded`) option is needed. We cannot squash them into
`-ir` because `-i[PREFIX]` has a special meaning: make a backup named
`tempconf[PREIX]`.
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.
"N/A" means the hardware just does not support this feature.
Currently "Fixed pipe TCL" is N/A for all supported models,
"Geometry programs" and "Tessellation programs" are N/A for some early
supported models.
We used to assume the users to config the kernel properly in xf86 video
drivers. But (1) xf86 video drivers and mesa drivers are not one-to-one
mapping; (2) there are wayland-based DEs where no xf86 video drivers are
installed.
Well, Vulkan is not an alternative of X, nor Wayland. It's an
alternative of OpenGL.
Change "libvulkan" to "Vulkan-Loader" by the way. "libvulkan" is a
library, and Vulkan-Loader is the name of the package providing it. The
URL is also updated because there is no download link at vulkan.org.
dconf is needed for non-DESTDIR install.
gtk3 is not directly used, but through libcanberra.
libdaemon is not used at all (I can't even find any Git history about it
in the upstream repo).
itstool is mentioned by some .po files but it seems the package actually
uses gettext instead of itstool. The NEWS mentions "switching from
intltool to gettext" so it seems itstool has never been really used at
all, too.
iso-codes seems not used. It was introduced for a language chooser
dialog 15 years ago (!) but the dialog is no more.
