Changeset 4eb513e for xsoft/graphweb/falkon.xml

Timestamp:

03/19/2021 04:32:57 AM (3 years ago)

Author:

Ken Moffat <ken@…>

Branches:

11.0, 11.1, 11.2, 11.3, 12.0, 12.1, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal

Children:

94f5f13

Parents:

64b8189

Message:

Update qtwebengine to 5.15.3 from git.

This is a lot bigger and slower to build.

Downgrade the 'Caution's in qtwebengien and falkon to 'Warning's.
I am not yet suggesting we should deprecate those two packages,
but users should start to ask themselves whether the want to use
a package where the upstreams are happy to stick with python2
and have no interest in running on current glibc.

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@24382 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:

• xsoft/graphweb/falkon.xml (modified) (2 diffs)

xsoft/graphweb/falkon.xml

@@ -42 +42 @@
     </para>
 
-    <caution>
+    <warning>
       <para>
-        Falkon re;lies on QtWebEngine. That uses a forked copy of chromium, and
+        Falkon relies on QtWebEngine. That uses a forked copy of chromium, and
         is therefore vulnerable to many issues found there. The Qt developers
         have always preferred to make releases at the same time as the rest of Qt
@@ -50 +50 @@
         Qt6, the 5.15.3 and later Qt-5.15 releases are initially only available
         to paying customers. QtWebEngine is something of an exception because of
-        its LGPL licence, but the source in git and its forked submodules is not
-        neatly packaged. Until someone is able to build this on BLFS, using
-        falkon leaves you open you to unpatched security vulnerabilities.
+        its LGPL licence, but getting the git sources (with the forked chromium
+        submodule) to a point where they will successfully build on a current
+        BLFS system can take a lot of effort. Be aware that future fixes for
+        vulnerabilities might be very delayed, to the extent that you might wish
+        to consider using a different browser.
       </para>
-    </caution>
+    </warning>
 
     &lfs101_checked;