Changeset ecffcbbc for xsoft/graphweb/firefox.xml

Timestamp:

11/13/2017 10:27:59 AM (6 years ago)

Author:

Pierre Labastie <pieere@…>

Branches:

10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, perl-modules, 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:

dd26d4d

Parents:

d378cf05

Message:

Change layout of the paragraph about tests in firefox, so that the test
instruction is in a <command> tag

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

File:

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

xsoft/graphweb/firefox.xml

@@ -76 +76 @@
         <para>
           Optional patch to allow system versions of <xref linkend="graphite2"/>
-          and <xref linkend="harfbuzz"/>
+          and <xref linkend="harfbuzz"/>:
           <ulink url="&patch-root;/firefox-&firefox-version;-system_graphite2_harfbuzz-1.patch"/>
         </para>
@@ -350 +350 @@
       The <filename>mozconfig</filename> above disables the tests because
       they use a lot more time and disk space for no obvious benefit. If
-      you have nevertheless enabled them, you can run the tests by executing:
-    </para>
-
-<screen><userinput>./mach gtest</userinput></screen>
-
-    <para>
-     This will require a network connection, and to be run from within an
-     Xorg session - there is a popup dialog when it fails to connect to
-     ALSA (that does not create a failed test). One or two tests will fail.
-     To see the details of the failure(s) you will need to log the output
-     from that command so that you can review it.
+      you have nevertheless enabled them, you can run the tests by executing
+      <command>./mach gtest</command>. This will require a network connection,
+      and to be run from within an Xorg session - there is a popup dialog
+      when it fails to connect to ALSA (that does not create a failed test).
+      One or two tests will fail.  To see the details of the failure(s) you
+      will need to log the output from that command so that you can review it.
     </para>