source: xsoft/graphweb/firefox.xml@ 93765fa

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
Last change on this file since 93765fa was 93765fa, checked in by Thomas Trepl (Moody) <thomas@…>, 3 years ago

Tags

  • Property mode set to 100644
File size: 24.8 KB
Line 
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
4 <!ENTITY % general-entities SYSTEM "../../general.ent">
5 %general-entities;
6
7 <!ENTITY firefox-download-http "&mozilla-http;/firefox/releases/&firefox-version;esr/source/firefox-&firefox-version;esr.source.tar.xz">
8 <!ENTITY firefox-download-ftp " ">
9 <!ENTITY firefox-md5sum "f81ca2f266ab3dafdd080f269bbb2286">
10 <!ENTITY firefox-size "366 MB">
11 <!-- NB with stylo, much of the build uses rust, and therefore cargo files.
12 But the extra cached cargo files, if any, seem to be minimal -->
13 <!ENTITY firefox-buildsize "6.7 GB (196 MB installed) without tests">
14 <!-- editors: with ff63 and rust-1.29, ./mach build -j4 is probably the
15 most practical way to get a timing on a machine with more cores, if taking
16 cores offline is not practical. If in doubt, round up -->
17 <!ENTITY firefox-time "28 SBU (on a typical 4-core machine) without tests">
18]>
19
20<sect1 id="firefox" xreflabel="Firefox-&firefox-version;">
21 <?dbhtml filename="firefox.html" ?>
22
23 <sect1info>
24 <date>$Date$</date>
25 </sect1info>
26
27 <title>Firefox-&firefox-version;</title>
28
29 <indexterm zone="firefox">
30 <primary sortas="a-Firefox">Firefox</primary>
31 </indexterm>
32
33 <sect2 role="package">
34 <title>Introduction to Firefox</title>
35
36 <para>
37 <application>Firefox</application> is a stand-alone browser based on the
38 <application>Mozilla</application> codebase.
39 </para>
40
41 &lfs110_checked;
42
43 <bridgehead renderas="sect3">Package Information</bridgehead>
44 <itemizedlist spacing="compact">
45 <listitem>
46 <para>
47 Download (HTTP): <ulink url="&firefox-download-http;"/>
48 </para>
49 </listitem>
50 <listitem>
51 <para>
52 Download (FTP): <ulink url="&firefox-download-ftp;"/>
53 </para>
54 </listitem>
55 <listitem>
56 <para>
57 Download MD5 sum: &firefox-md5sum;
58 </para>
59 </listitem>
60 <listitem>
61 <para>
62 Download size: &firefox-size;
63 </para>
64 </listitem>
65 <listitem>
66 <para>
67 Estimated disk space required: &firefox-buildsize;
68 </para>
69 </listitem>
70 <listitem>
71 <para>
72 Estimated build time: &firefox-time;
73 </para>
74 </listitem>
75 </itemizedlist>
76
77 <bridgehead renderas="sect3">Additional Downloads</bridgehead>
78 <itemizedlist spacing="compact">
79 <listitem>
80 <para>
81 Required patch:
82 <ulink url="&patch-root;/firefox-&firefox-version;esr-glibc234-1.patch"/>
83 </para>
84 </listitem>
85 <listitem>
86 <para>
87 Recommended patch:
88 <ulink url="&patch-root;/firefox-&firefox-version;esr-disable_rust_test-1.patch"/>
89 </para>
90 </listitem>
91 </itemizedlist>
92
93 <note>
94
95 <!-- temporary note, remove with firefox-legacy -->
96 <para>
97 With the 91 ESR series, firefox no-longer works on ftp: links.
98 If that is important to you, as a temporary measure (on non-glibc-2.34
99 systems) you can continue to use <xref linkend="firefox-legacy"/>
100 while you explore alternative approaches.
101 </para>
102 <!-- end of temporary note -->
103
104 <para>
105 The directory name is firefox-&firefox-version;
106 </para>
107
108 <para>
109 Extracting the tarball
110 will reset the permissions of the current directory to 0755 if you
111 have permission to do that. If you do this in a directory where
112 the sticky bit is set, such
113 as <filename class="directory">/tmp</filename> it will end with error
114 messages:
115 </para>
116
117<literallayout>tar: .: Cannot utime: Operation not permitted
118tar: .: Cannot change mode to rwxr-xr-t: Operation not permitted
119tar: Exiting with failure status due to previous errors
120</literallayout>
121
122 <para>
123 This does finish with non-zero status, but it does
124 <emphasis>NOT</emphasis> mean there is a real problem.
125 Do not untar as the <systemitem class="username">root</systemitem> user
126 in a directory where the sticky bit is set - that will unset it.
127 </para>
128
129 <para>
130 As with other large packages which use C++ (or rust), the SBU times
131 to build this vary more widely than you might expect. The build times
132 will increase significantly if your machine has to swap.
133 </para>
134
135 <!-- commented, by 78.0 it seems to work reliably
136 <para>
137 The mach build system (Python scripts) can be somewhat unreliable: if
138 the build fails and reports an Error, it can still return a status of
139 success, causing a scripted build to try to install (which does not rerun
140 the build), fail during the preparations for installing, but still exit
141 with a status of success. Also, on occasion it may limit itself to only
142 running one set of jobs - that will make the build take about 3 times as
143 long as running with four sets of jobs.
144 </para>-->
145
146 <para>
147 Although upstream prefer to use <application>PulseAudio</application>,
148 for the moment <application>Alsa</application> can still be used. Both
149 may need runtime configuration to get sound working.
150 </para>
151 </note>
152
153 <bridgehead renderas="sect3">Firefox Dependencies</bridgehead>
154
155 <bridgehead renderas="sect4">Required</bridgehead>
156 <para role="required">
157 <xref linkend="autoconf213"/>,
158 <xref linkend="cbindgen"/>,
159 <xref linkend="dbus-glib"/>,
160 both <xref linkend="gtk3"/> and
161 <xref linkend="gtk2"/>,
162 <xref linkend="libnotify"/>,
163 <xref linkend="llvm"/> (clang, used for bindgen even if using gcc),
164 <xref linkend="nodejs"/>,
165 <xref linkend="nss"/>,
166 <xref linkend="pulseaudio"/>
167 (or
168 <xref linkend="alsa-lib"/> if you edit the mozconfig;
169 now deprecated by mozilla), in either case please read the
170 Configuration Information,
171 <!-- rustc is required by cbindgen so not needed here
172 <xref linkend="rust"/>,-->
173 <xref linkend="python3"/> (rebuilt after installing <xref linkend="sqlite"/>),
174 <xref linkend="startup-notification"/>,
175 <xref linkend="unzip"/>,
176 <xref linkend="yasm"/>, and
177 <xref linkend="zip"/>
178 </para>
179
180 <bridgehead renderas="sect4">Recommended</bridgehead>
181 <para role="recommended">
182 <xref linkend="icu"/>,
183 <xref linkend="libevent"/>,
184 <xref linkend="libwebp"/>,
185 <xref linkend="nasm"/>
186 </para>
187
188 <note>
189 <para>
190 If you don't install recommended dependencies, then internal copies of
191 those packages will be used. They might be tested to work, but they can
192 be out of date or contain security holes.
193 </para>
194 </note>
195
196 <bridgehead renderas="sect4">Optional</bridgehead>
197 <para role="optional">
198 <xref linkend="curl"/>,
199 <xref linkend="doxygen"/>,
200 <xref role="runtime" linkend="ffmpeg"/> (runtime, to play mov, mp3 or mp4 files),
201 <!-- <phrase revision="sysv"><ulink url="https://sourceforge.net/projects/liboauth/files/">liboauth</ulink></phrase> -->
202 <xref linkend="liboauth"/>,
203 <xref linkend="openjdk"/>,
204 <xref linkend="valgrind"/>,
205 <xref linkend="wget"/>,
206 <xref linkend="wireless_tools"/>,
207 <ulink url="https://github.com/libproxy/libproxy">libproxy</ulink>
208 </para>
209
210 <para condition="html" role="usernotes">
211 User Notes: <ulink url="&blfs-wiki;/firefox"/>
212 </para>
213 </sect2>
214
215 <sect2 role="installation">
216 <title>Installation of Firefox</title>
217
218 <para>
219 The configuration of <application>Firefox</application> is accomplished
220 by creating a <filename>mozconfig</filename> file containing the desired
221 configuration options. A default <filename>mozconfig</filename> is
222 created below. To see the entire list of available configuration options
223 (and an abbreviated description of some of them), issue <command>./mach
224 configure &amp;&amp; ./configure --help | less</command>. You may also
225 wish to review the entire file and uncomment any other desired options.
226 Create the file by issuing the following command:
227 </para>
228
229<screen><userinput>cat &gt; mozconfig &lt;&lt; "EOF"
230<literal># If you have a multicore machine, all cores will be used by default.
231
232# If you have installed (or will install) wireless-tools, and you wish
233# to use geolocation web services, comment out this line
234ac_add_options --disable-necko-wifi
235
236# API Keys for geolocation APIs - necko-wifi (above) is required for MLS
237# Uncomment the following line if you wish to use Mozilla Location Service
238#ac_add_options --with-mozilla-api-keyfile=$PWD/mozilla-key
239
240# Uncomment the following line if you wish to use Google's geolocaton API
241# (needed for use with saved maps with Google Maps)
242#ac_add_options --with-google-location-service-api-keyfile=$PWD/google-key
243
244# startup-notification is required since firefox-78
245
246# Uncomment the following option if you have not installed PulseAudio
247#ac_add_options --disable-pulseaudio
248# or uncomment this if you installed alsa-lib instead of PulseAudio
249#ac_add_options --enable-alsa
250
251# Uncomment this line if you are building on an i686 system to fix a build
252# failure due to invalid ASM code.
253#ac_add_options --with-system-libvpx
254
255# Comment out following options if you have not installed
256# recommended dependencies:
257ac_add_options --with-system-libevent
258ac_add_options --with-system-webp
259ac_add_options --with-system-nspr
260ac_add_options --with-system-nss
261ac_add_options --with-system-icu
262
263# Do not specify the gold linker which is not the default. It will take
264# longer and use more disk space when debug symbols are disabled.
265
266# libdavid (av1 decoder) requires nasm. Uncomment this if nasm
267# has not been installed.
268#ac_add_options --disable-av1
269
270# You cannot distribute the binary if you do this
271ac_add_options --enable-official-branding
272
273# Stripping is now enabled by default.
274# Uncomment these lines if you need to run a debugger:
275#ac_add_options --disable-strip
276#ac_add_options --disable-install-strip
277
278# Disabling debug symbols makes the build much smaller and a little
279# faster. Comment this if you need to run a debugger. Note: This is
280# required for compilation on i686.
281ac_add_options --disable-debug-symbols
282
283# The elf-hack is reported to cause failed installs (after successful builds)
284# on some machines. It is supposed to improve startup time and it shrinks
285# libxul.so by a few MB - comment this if you know your machine is not affected.
286ac_add_options --disable-elf-hack
287
288# The BLFS editors recommend not changing anything below this line:
289ac_add_options --prefix=/usr
290ac_add_options --enable-application=browser
291ac_add_options --disable-crashreporter
292ac_add_options --disable-updater
293# enabling the tests will use a lot more space and significantly
294# increase the build time, for no obvious benefit.
295ac_add_options --disable-tests
296
297# The default level of optimization again produces a working build with gcc.
298ac_add_options --enable-optimize
299
300ac_add_options --enable-system-ffi
301ac_add_options --enable-system-pixman
302
303ac_add_options --with-system-jpeg
304ac_add_options --with-system-png
305ac_add_options --with-system-zlib
306
307# The following option unsets Telemetry Reporting. With the Addons Fiasco,
308# Mozilla was found to be collecting user's data, including saved passwords and
309# web form data, without users consent. Mozilla was also found shipping updates
310# to systems without the user's knowledge or permission.
311# As a result of this, use the following command to permanently disable
312# telemetry reporting in Firefox.
313unset MOZ_TELEMETRY_REPORTING
314
315mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/firefox-build-dir</literal>
316EOF</userinput></screen>
317
318 <para>
319 Compile <application>Firefox</application> by issuing the following
320 commands:
321 </para>
322
323 <para>
324 Apply a patch which allows compilation on systems running glibc-2.34:
325 </para>
326
327<screen><userinput>patch -Np1 -i ../firefox-&firefox-version;esr-glibc234-1.patch</userinput></screen>
328
329 <para>
330 Now apply a patch which works around unexplained failures on some machines
331 (a message that a python check on libgkrust.a identified 1 networking
332 function, getsockname) in the rust static library.
333 </para>
334
335<screen><userinput>patch -Np1 -i ../firefox-&firefox-version;esr-disable_rust_test-1.patch</userinput></screen>
336
337 <para>
338 If the geolocation APIs are needed:
339 </para>
340
341 <note>
342 <para>
343 <!-- Taken from Arch Linux - an immensely helpful link - Thanks -->
344 The Google and Mozilla API Keys below are specific to LFS. If using
345 these instructions for another distro, or if you intend to distribute
346 binary copies of the software using these instructions, please obtain
347 your own keys following the instructions located at
348 <ulink url="http://www.chromium.org/developers/how-tos/api-keys"/> and
349 <ulink url="https://location.services.mozilla.com/api"/> respectively.
350 <!-- BLFS Devs, register an account at Google with your
351 @linuxfromscratch.org email address, and I'll make you an administrator
352 for the 'Google APIs for LFS' project (where the API and OAuth keys
353 were created for use in the book).-->
354 </para>
355 </note>
356
357<screen><userinput>echo "AIzaSyDxKL42zsPjbke5O8_rPVpVrLrJ8aeE9rQ" > google-key
358echo "613364a7-9418-4c86-bcee-57e32fd70c23" > mozilla-key</userinput></screen>
359
360 <note>
361
362 <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
363 href="../../xincludes/mozshm.xml"/>
364
365 <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
366 href="../../xincludes/mozmach.xml"/>
367
368 </note>
369 <!--
370 <para>
371 If you are building on i686, apply a fix to prevent Internal Compiler
372 Errors in GCC-7+:
373 </para>
374
375<screen><userinput remap="pre">case $(uname -m) in
376 i?86) sed -i "562 s/mips64/i386/" gfx/skia/skia/third_party/skcms/src/Transform_inl.h ;;
377esac</userinput></screen>
378 -->
379<!--<para>
380 Apply a patch to allow this to be compiled with <xref linkend="rust"/>:
381 </para>
382
383<screen><userinput remap="pre">patch -p1 -i ../firefox-&firefox-version;esr-rustc1470-1.patch</userinput></screen>-->
384
385 <para>
386 Now invoke the Python <command>mach</command> script to compile the package.
387 </para>
388
389<screen><userinput>export CC=gcc CXX=g++ &amp;&amp;
390export MACH_USE_SYSTEM_PYTHON=1 &amp;&amp;
391export MOZBUILD_STATE_PATH=${PWD}/mozbuild &amp;&amp;
392./mach configure &amp;&amp;
393./mach build</userinput></screen>
394
395 <para>
396 The <filename>mozconfig</filename> above disables the tests because
397 they use a lot more time and disk space for no obvious benefit. If
398 you have nevertheless enabled them, you can run the tests by executing
399 <command>./mach gtest</command>. This will require a network connection,
400 and to be run from within an Xorg session - there is a popup dialog
401 when it fails to connect to ALSA (that does not create a failed test).
402 One or two tests will fail. To see the details of the failure(s) you
403 will need to log the output from that command so that you can review it.
404 </para>
405
406 <para>
407 Now, as the <systemitem class="username">root</systemitem> user:
408 </para>
409
410<screen role="root"><userinput>MACH_USE_SYSTEM_PYTHON=1 ./mach install</userinput></screen>
411
412 <para>
413 Empty the environment variables which were set above:
414 </para>
415
416<screen><userinput>unset CC CXX MACH_USE_SYSTEM_PYTHON MOZBUILD_STATE_PATH</userinput></screen>
417
418 </sect2>
419
420 <sect2 role="commands">
421 <title>Command Explanations</title>
422
423<!--<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
424 href="../../xincludes/SIOCGSTAMP.xml"/>-->
425
426 <para>
427 <command>export CC=gcc CXX=g++ ...</command>: Upstream now prefer
428 <application>clang</application> so that they can use one compiler
429 everywhere. On the X86 architectures <application>clang</application>
430 now appears to support most of the same security-hardening options as
431 <application>GCC</application>.
432 <!-- supported in llvm-11
433 but the newer
434 <literal>-fstack-clash-protection</literal> is still not supported.-->
435 With the current versions and the default flags,
436 <application>GCC</application> creates a marginally bigger build but
437 takes typically 2 SBU less time on a 4-core machine using the mozconfig
438 above.
439 </para>
440
441 <para>
442 <command>export MOZBUILD_STATE_PATH=${PWD}/mozbuild</command>: The build
443 is now supposed to tell you that it intends to create <filename
444 class="directory">~/.mozbuild</filename>, and offer you an option to
445 press &lt;ENTER&gt; to accept this, or Ctrl-C to cancel and restart the
446 build after specifying the directory. In practice, the message may not
447 appear until after &lt;ENTER&gt; is keyed, i.e. the build stalls.
448 </para>
449
450 <para>
451 That directory is used for a (probably random) telemetry identifier.
452 Creating this in the build directory, and deleting that after the
453 installation, prevents it being used. If you wish to participate in
454 telemetry, export MOZBUILD_STATE_PATH to point to its default directory
455 and remove the entry from the <filename>mozconfig</filename>.
456 </para>
457
458 <para>
459 <command>MACH_USE_SYSTEM_PYTHON=1</command>: Use the system python
460 to create a virtual environment for <command>mach</command> without
461 downloading any python wheels.
462 </para>
463
464 <para>
465 <command>./mach configure</command>: This validates the supplied
466 dependencies and the <filename>mozconfig</filename>.
467 </para>
468
469 <para>
470 <option>./mach build --verbose</option>: Use this alternative if you
471 need details of which files are being compiled, together with any C or
472 C++ flags being used. But do not add '--verbose' to the install command,
473 it is not accepted there.
474 </para>
475
476 <para>
477 <option>./mach build -jN</option>: The build should, by default, use
478 all the online CPU cores. If using all the cores causes the build to swap
479 because you have insufficient memory, using fewer cores can be faster.
480 </para>
481
482<!--
483 <para>
484 <command>mkdir -pv /usr/lib/mozilla/plugins</command>: This ensures
485 that <filename class="directory">/usr/lib/mozilla/plugins/</filename>
486 exists.
487 </para>
488
489 <para>
490 <command>ln -sv ... /usr/lib/firefox/browser</command>:
491 This command creates a symbolic link to <filename
492 class="directory">/usr/lib/mozilla/plugins</filename>. It's not really
493 needed, as <application>Firefox</application> checks <filename
494 class="directory">/usr/lib/mozilla/plugins</filename> by default, but the
495 symbolic link is made to keep all the plugins installed in one folder.
496 </para>
497-->
498
499 </sect2>
500
501 <sect2 role="configuration">
502 <title>Configuring Firefox</title>
503
504 <para>
505 If you use a desktop environment like <application>Gnome</application> or
506 <application>KDE</application> you may like to create a
507 <filename>firefox.desktop</filename> file so that
508 <application>Firefox</application> appears in the panel's menus. <!--If you
509 didn't enable startup-notification in your mozconfig change the
510 StartupNotify line to false.--> As the
511 <systemitem class="username">root</systemitem> user:
512 </para>
513
514<screen role="root"><userinput>mkdir -pv /usr/share/applications &amp;&amp;
515mkdir -pv /usr/share/pixmaps &amp;&amp;
516
517cat &gt; /usr/share/applications/firefox.desktop &lt;&lt; "EOF" &amp;&amp;
518<literal>[Desktop Entry]
519Encoding=UTF-8
520Name=Firefox Web Browser
521Comment=Browse the World Wide Web
522GenericName=Web Browser
523Exec=firefox %u
524Terminal=false
525Type=Application
526Icon=firefox
527Categories=GNOME;GTK;Network;WebBrowser;
528MimeType=text/html;text/xml;application/xhtml+xml;application/vnd.mozilla.xul+xml;text/mml;x-scheme-handler/http;x-scheme-handler/https;
529StartupNotify=true</literal>
530EOF
531
532ln -sfv /usr/lib/firefox/browser/chrome/icons/default/default128.png \
533 /usr/share/pixmaps/firefox.png</userinput></screen>
534
535 <sect3><title>Configuration Information</title>
536
537 <para>
538 The application settings for firefox are accessible by keying
539 <command>about:config</command> in the address bar.
540 </para>
541
542 <para>
543 Occasionally, getting working sound in
544 <application>firefox</application> can be a problem. Although upstream
545 prefers pulseaudio,
546 on balance using <application>Alsa</application> may be easier.
547 </para>
548
549 <para>
550 If you enabled <application>Alsa</application> for sound, you may need
551 to alter one variable to get working sound. If you run
552 <command>firefox</command> from a term and try to play something with
553 sound you might encounter error messages like:
554 </para>
555
556 <para>
557 <literal>Sandbox: seccomp sandbox violation: pid 3941, tid 4030,
558 syscall 16, args 48 2147767296 139909894784796 0 0 0.</literal>
559 </para>
560
561 <para>
562 That was on x86_64, on i686 the syscall number is 54. To allow this
563 syscall, in <command>about:config</command> change
564 <command>security.sandbox.content.syscall_whitelist</command> to 16
565 (or 54 if using i686).
566 </para>
567
568 <para>
569 If you use <command>pulseaudio</command> in a Desktop Environment, it
570 might already be started by that DE. But if it is not, although
571 firefox-57 managed to start it, firefox-58 did not. If you run
572 <command>firefox</command> from a term and this problem is present,
573 trying to play sound will
574 encounter error messages warning <literal>Can't get cubeb
575 context!</literal>
576 </para>
577
578 <para>
579 The fix for this is to close firefox, start pulseaudio to check it
580 does start (if not, read the information on Configuring in <xref
581 linkend="pulseaudio"/>) and restart firefox to check it is working.
582 If it now works, add the following to your <filename>~/.xinitrc</filename>:
583<phrase revision="sysv">
584<literal>pulseaudio --verbose --log-target=syslog&amp;</literal></phrase>
585<phrase revision="systemd">
586<literal>pulseaudio --verbose --log-target=journald&amp;</literal></phrase>
587 (unfortunately, on some systems this does not work).
588 </para>
589
590 <para>
591 You may wish to use multiple profiles within firefox. To do that, invoke
592 firefox as <command>firefox --ProfileManager</command>. You can also
593 check which profile is currently in use from
594 <command>about:profiles</command>.
595 </para>
596
597 <para>
598 Although WebRender (using the GPU for compositing) is not used by
599 default, it now appears to work well on supported hardware (ATI, Nvidia
600 and Intel GPUs with Mesa-18 or later. For an explanation, please see
601 <ulink
602 url="https://hacks.mozilla.org/2017/10/the-whole-web-at-maximum-fps-how-webrender-gets-rid-of-jank/">hacks.mozilla.org</ulink>.
603 The only downside seems to be that on a machine with limited RAM it might
604 use more RAM.
605 </para>
606
607 <para>
608 To check if WebRender is being used, look in about:support. In the Graphics
609 section Compositing will either show 'Basic' (i.e. not in use) or
610 'WebRender'. To enable it, go to about:config and change gfx.webrender.all
611 to True. You will need to restart firefox.
612 </para>
613
614 <para>
615 It may be useful to mention the processes from firefox which can appear in
616 <command>top</command> - as well as firefox itself, there may be multiple
617 Web Content processes, and now an RDD Process (Remote Data Decoder) which
618 appears when playing web videos encoded with av1 (libdav1d). If WebRender
619 has been enabled, a GPU Process will also appear when firefox has to
620 repaint (e.g. scrolling, opening a new tab, or playing a video).
621 </para>
622
623 </sect3>
624 </sect2>
625
626 <sect2 role="content">
627 <title>Contents</title>
628
629 <segmentedlist>
630 <segtitle>Installed Programs</segtitle>
631 <segtitle>Installed Libraries</segtitle>
632 <segtitle>Installed Directory</segtitle>
633
634 <seglistitem>
635 <seg>
636 firefox
637 </seg>
638 <seg>
639 Numerous libraries, browser components, plugins, extensions, and
640 helper modules installed in /usr/lib/firefox
641 </seg>
642 <seg>
643 /usr/lib/firefox and /usr/lib/mozilla
644 </seg>
645 </seglistitem>
646 </segmentedlist>
647
648 <variablelist>
649 <bridgehead renderas="sect3">Short Descriptions</bridgehead>
650 <?dbfo list-presentation="list"?>
651 <?dbhtml list-presentation="table"?>
652
653 <varlistentry id="firefox-prog">
654 <term><command>firefox</command></term>
655 <listitem>
656 <para>
657 is a <application>GTK+-3</application> internet browser that uses
658 the Mozilla Gecko rendering engine
659 </para>
660 <indexterm zone="firefox firefox-prog">
661 <primary sortas="b-firefox">firefox</primary>
662 </indexterm>
663 </listitem>
664 </varlistentry>
665
666 </variablelist>
667
668 </sect2>
669
670</sect1>
Note: See TracBrowser for help on using the repository browser.