source: xsoft/graphweb/firefox.xml@ e8d45427

10.0 10.1 11.0 9.0 9.1 ken/refactor-virt lazarus qt5new trunk xry111/git-date xry111/git-date-for-trunk xry111/git-date-test
Last change on this file since e8d45427 was e8d45427, checked in by Ken Moffat <ken@…>, 2 years ago

Firefox-68.0.1 and provisionally fix it for the linux-5.2 API change.

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

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