linux-from-scratch/glfs
1
0
Fork 0
mirror of https://github.com/Zeckmathederg/glfs.git synced 2025-02-03 06:27:16 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

Updated seamonkey to 2.5

Browse Source 
git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@9051 af4574ff-66df-0310-9fd7-8a98e5e911e0
This commit is contained in:
Andrew Benton 2011-12-02 17:02:01 +00:00
parent 6bf551c8d8
commit 88cec02f58
4 changed files with 131 additions and 384 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
general.ent
View File

@ -783,7 +783,7 @@ $Date$
<!ENTITY openoffice-version "3.2.1">
<!-- Chapter 36 -->
<!ENTITY seamonkey-version "2.0">
<!ENTITY seamonkey-version "2.5">
<!ENTITY firefox-version "8.0.1">
<!ENTITY galeon-version "2.0.1">

3
introduction/welcome/changelog.xml
View File

@ -44,6 +44,9 @@
<listitem>
<para>December 2nd, 2011</para>
<itemizedlist>
<listitem>
<para>[abenton] - Updated seamonkey to 2.5.</para>
</listitem>
<listitem>
<para>[abenton] - Updated libvpx to v0.9.7.</para>
</listitem>

16
xsoft/graphweb/firefox.xml
View File

@ -74,7 +74,8 @@
<bridgehead renderas="sect4">Recommended</bridgehead>
<para role="recommended"><xref linkend="yasm"/> or
<xref linkend="libvpx"/>.</para>
<xref linkend="libvpx"/> (to allow <application>Firefox</application> to
play webm videos).</para>
<bridgehead renderas="sect4">Optional</bridgehead>
<para role="optional"><xref linkend="dbus-glib"/>,
@ -241,6 +242,19 @@ chown -R -v root:root /usr/lib/firefox-&firefox-version;</userinput></screen>
</sect2>
<sect2 role="configuration">
<title>Configuring Firefox</title>
<para>If you deleted the <option>--disable-webm</option> option from your
<filename>mozconfig</filename>, your <application>Firefox</application>
can play most YouTube videos without the need for the flash plugin. To
enable this, go to <ulink
url="http://www.youtube.com/html5">http://www.youtube.com/html5</ulink>
and click on &apos;Join the HTML5 Trial&apos; (needs cookies
enabled).</para>
</sect2>
<sect2 role="content">
<title>Contents</title>

494
xsoft/graphweb/seamonkey.xml
View File

@ -6,14 +6,10 @@
<!ENTITY seamonkey-download-http "http://ftp.mozilla.org/pub/mozilla.org/seamonkey/releases/&seamonkey-version;/source/seamonkey-&seamonkey-version;.source.tar.bz2">
<!ENTITY seamonkey-download-ftp "ftp://ftp.mozilla.org/pub/mozilla.org/seamonkey/releases/&seamonkey-version;/source//seamonkey-&seamonkey-version;.source.tar.bz2">
<!ENTITY seamonkey-md5sum "494608587e3ba4e4cc2e754d95154435">
<!ENTITY seamonkey-md5sum "f0f0dd652ad5ee9458d86aeb626615bd">
<!ENTITY seamonkey-size "57.5 MB">
<!ENTITY seamonkey-buildsize "844 MB">
<!ENTITY seamonkey-time "10.8 SBU">
<!--
<!ENTITY seamonkey-enigmail-version "0.95.6">
<!ENTITY seamonkey-enigmail-download "http://www.mozilla-enigmail.org/download/source/enigmail-&seamonkey-enigmail-version;.tar.gz">
<!ENTITY seamonkey-enigmail-md5sum "cfbe6ff77f80a349b396829757ad952a"> -->
]>
<sect1 id="seamonkey" xreflabel="SeaMonkey-&seamonkey-version;">
@ -35,27 +31,19 @@
<para><application>SeaMonkey</application> is a browser suite, the Open
Source sibling of <application>Netscape</application>. It includes the
browser, composer, mail and news clients, and an
IRC client. It is the follow-on to the Mozilla browser suite.</para>
browser, composer, mail and news clients, and an IRC client. It is the
follow-on to the Mozilla browser suite.</para>
<para>The Mozilla project also hosts two subprojects that aim to satisfy
the needs of users who don&apos;t need the complete browser suite or prefer to
have separate applications for browsing and e-mail. These subprojects are
<ulink url="http://www.mozilla.com/firefox/">Mozilla Firefox</ulink>, (a
stand-alone browser based on the <application>Mozilla</application> source
code) and <ulink url="http://www.mozilla.com/thunderbird/">Mozilla
Thunderbird</ulink>, (a stand-alone mail/newsgroup client based on the
<application>Mozilla</application> source code). The build instructions for
these two applications are discussed in separate sections:</para>
the needs of users who don&apos;t need the complete browser suite or prefer
to have separate applications for browsing and e-mail. These subprojects
are <xref linkend="firefox"/> and <xref linkend="thunderbird"/>. Both are
based on the <application>Mozilla</application> source code.
<!-- if you delete the - -enable-application=suite option,
<application>Thunderbird</application> can be built from this source
tarball.--></para>
<itemizedlist>
<listitem>
<para><xref linkend="firefox"/></para>
</listitem>
<listitem>
<para><xref linkend="thunderbird"/></para>
</listitem>
</itemizedlist>
&lfs70_checked;
<bridgehead renderas="sect3">Package Information</bridgehead>
<itemizedlist spacing="compact">
@ -78,50 +66,39 @@
<para>Estimated build time: &seamonkey-time;</para>
</listitem>
</itemizedlist>
<!--
<para>To enable the <application>Enigmail</application> extension to the
<application>SeaMonkey</application> mail client, you'll need to download
the tarball listed below. The <application>Enigmail</application> extension
allows users to access the authentication and encryption features provided
by the <application>GnuPG</application> package. The
<application>Enigmail</application> extension will not operate correctly
unless you have <xref linkend="gnupg"/> or <xref linkend="gnupg2"/>
installed.</para>
<itemizedlist spacing='compact'>
<listitem>
<para><ulink url="&seamonkey-enigmail-download;"/></para>
</listitem>
<listitem>
<para>Download MD5 sum (Enigmail): &seamonkey-enigmail-md5sum;</para>
</listitem>
</itemizedlist>
-->
<bridgehead renderas="sect3">SeaMonkey Dependencies</bridgehead>
<bridgehead renderas="sect4">Required</bridgehead>
<para role="required"><xref linkend="gtk2"/>,
<xref linkend="libidl"/>, and
<xref linkend="zip"/></para>
<para role="required"><xref linkend="alsa-lib"/>, <xref linkend="gtk2"/>,
<xref linkend="libidl"/>, and <xref linkend="zip"/></para>
<note>
<para><xref linkend="libjpeg"/> should have been installed before
<application>GTK+</application> and should exist on your system. If
for some reason you haven&apos;t installed <application>libjpeg</application>,
you should remove the <option>--with-system-jpeg</option> option from the
<filename>.mozconfig</filename> file created below.</para>
<para><application>libjpeg</application> and
<application>libpng</application> (patched for apng support) should have
been installed before <application>gdk-pixbuf</application> and should
exist on your system. If for some strange reason you haven't installed
them, you should remove the <option>--with-system-jpeg</option> and
<option>--with-system-png</option> options from the
<filename>mozconfig</filename> file created below.</para>
</note>
<bridgehead renderas="sect4">Recommended</bridgehead>
<para role="recommended"><xref linkend="nss"/> (if you will be installing
any other package that utilizes NSS/NSPR, such as
<application>Firefox</application>, <application>Thunderbird</application>,
<application>Evolution</application>, or
<application>OpenOffice</application>)</para>
<para role="recommended"><xref linkend="yasm"/> or
<xref linkend="libvpx"/> (to allow <application>Seamonkey</application> to
play webm videos).</para>
<bridgehead renderas="sect4">Optional</bridgehead>
<para role="optional"><xref linkend="unzip"/> and
<xref linkend="libgnomeui"/> (to build the gnomevfs extension)</para>
<para role="optional"><xref linkend="dbus-glib"/>,
<xref linkend="startup-notification"/>, <xref linkend="sqlite"/>,
<ulink url="http://www.webmproject.org/code/">libvpx</ulink>,
<ulink url="http://sourceforge.net/projects/hunspell/">Hunspell</ulink>,
<xref linkend="doxygen"/>, <xref linkend="gnome-vfs"/> and
<xref linkend="libgnomeui"/> (for gnome integration),
<xref linkend="libnotify"/>, <xref linkend="nspr"/>, <xref linkend="nss"/>,
<xref linkend="unzip"/>, <xref linkend="wireless_tools"/>,
<ulink url="http://www.valgrind.org/">Valgrind</ulink> (only for testing
the jemalloc code) and <xref linkend="wget"/></para>
<para condition="html" role="usernotes">User Notes:
<ulink url="&blfs-wiki;/seamonkey"/></para>
@ -132,368 +109,123 @@
<title>Installation of SeaMonkey</title>
<para>The configuration of <application>SeaMonkey</application> is
accomplished by creating a <filename>.mozconfig</filename> file containing
the desired configuration options. A default <filename>.mozconfig</filename>
accomplished by creating a <filename>mozconfig</filename> file containing
the desired configuration options. A default <filename>mozconfig</filename>
file is created below. To see the entire list of available configuration
options (and an abbreviated description of each one), issue
<command>./configure --help</command>. Additional information can also be
found below in the section titled <xref linkend="add-mozconfig"/>. If you
are going to use system-installed versions of the
<application>NSS</application> and <application>NSPR</application>
libraries, ensure you uncomment the two lines near the bottom of the file. If
you would prefer to download the file instead of creating it by typing or
cut-and-pasting, you can find it at <ulink
url="&files-anduin;/seamonkey-&seamonkey-version;-mozconfig"/>
(the file must be installed in the root of the source tree
<filename class='directory'>mozilla</filename> directory, and named
<filename>.mozconfig</filename>). Create the file by issuing the following
command:</para>
<command>./configure --help</command>. You may also wish to review the
entire file and uncomment any other desired options. Create the file by
issuing the following command:</para>
<screen><?dbfo keep-together="auto"?><userinput>cat &gt; .mozconfig &lt;&lt; "EOF"
<literal># This file contains the options used in the SeaMonkey build. You may
# need to specify additional options for your specific build needs.
# Use the information provided by running './configure --help' to
# help you determine if you need to add any additional options.
# Some additional options can be added by uncommenting the examples
# in this file or adding options by inserting a line containing
# 'ac_add_options --some-option-you-need'.
# If you have a multicore machine you can speed up the build by running
# several jobs at once, but if you have a single core, delete this line:
mk_add_options MOZ_MAKE_FLAGS="-j4"
# If you have installed Yasm delete this option:
ac_add_options --disable-webm
# Create an object directory and specify to build the package in that
# directory. If desired, modify the location of the object directory
# to a directory inside the source tree by removing '../' from the
# line below.
mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/../seamonkey-build
# If you have installed DBus-Glib delete this option:
ac_add_options --disable-dbus
# This option is used to specify that the SeaMonkey suite is
# being built and to use all the default options for SeaMonkey.
# If you have installed wireless-tools delete this option:
ac_add_options --disable-necko-wifi
# If you have installed libnotify delete this option:
ac_add_options --disable-libnotify
# If you have installed nss and nspr uncomment these two lines:
# ac_add_options --with-system-nspr
# ac_add_options --with-system-nss
# Uncomment these if you have installed them:
# ac_add_options --enable-system-sqlite
# ac_add_options --enable-system-lcms
# ac_add_options --with-system-libvpx
# ac_add_options --enable-startup-notification
mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/moz-build-dir
ac_add_options --enable-application=suite
# Specify the installation prefix. If you would prefer SeaMonkey
# installed in a different prefix, modify the line below to fit
# your needs. You'll also need to modify some of the instructions in
# the BLFS book to point to your desired prefix.
ac_add_options --prefix=/usr
# These options are used so that the SeaMonkey binaries are linked to
# the system-installed copies of the specified libraries instead of
# the source tree code which may not be the most recent versions.
ac_add_options --with-system-zlib
ac_add_options --with-system-png
ac_add_options --with-system-jpeg
ac_add_options --enable-pthreads
ac_add_options --enable-system-ffi
ac_add_options --enable-system-jpeg
ac_add_options --enable-system-png
ac_add_options --enable-system-cairo
# This option specifies to include support for rendering the HTML
# &lt;canvas&gt;&lt;/canvas&gt; tag in the SeaMonkey browser.
ac_add_options --enable-canvas
# This option is used so that the debugging symbols are removed from
# the installed binaries during the installation process. Comment out
# this option if you may have a need to retain the debugging symbols
# in the installed binaries. Note that this can substantially
# increase the size of the installed binaries.
ac_add_options --enable-strip
# This option is added so that test libraries and programs are not
# built. These would only be required for debugging purposes.
ac_add_options --disable-tests
# This option is added so that the Mozilla Installer program is not
# built or installed. The program is not required for a BLFS
# installation of SeaMonkey.
ac_add_options --enable-system-zlib
ac_add_options --enable-shared
ac_add_options --disable-static
ac_add_options --disable-debug
ac_add_options --disable-crashreporter
ac_add_options --disable-installer
# This option is used to disable the a11y support in the SeaMonkey
# binaries. Comment out this option if you require a11y support.
ac_add_options --disable-accessibility
# This option is used to enable support for rendering SVG files in the
# SeaMonkey browser.
ac_add_options --enable-svg
# This option is used to enable source tree included LDAP support in
# the SeaMonkey binaries.
ac_add_options --enable-ldap
# These two options enable support for building SeaMonkey with
# system-installed versions of the Network Security Services (NSS)
# and Netscape Portable Runtime (NSPR) libraries. Uncomment both
# lines to enable support for system-installed NSS/NSPR.
#ac_add_options --with-system-nspr
#ac_add_options --with-system-nss
# Uncomment this option if you desire support for dual-monitor
# display of SeaMonkey using the X-Window Xinerama libraries.
#ac_add_options --enable-xinerama
# Complex scripts such as Thai can only be rendered in SeaMonkey with the
# help of Pango. This option significantly slows rendering, so only use
# it if necessary.
#ac_add_options --enable-pango
# This option identifies the default binary directory of the SeaMonkey
# installation and is used to locate SeaMonkey's installed files. This
# option is not required for end-user browsing, and is only used for
# development purposes.
#ac_add_options --with-default-mozilla-five-home=/usr/lib/seamonkey-&seamonkey-version;</literal>
EOF</userinput></screen>
ac_add_options --disable-updater
ac_add_options --disable-tests</userinput></screen>
<para>Compile <application>SeaMonkey</application> by running the
following command:</para>
<screen><userinput> make -f client.mk build</userinput></screen>
<!--
<para>If you're building the <application>SeaMonkey</application>
mail/newsgroup client and plan to install the
<application>Enigmail</application> extension, issue the following
commands:</para>
<screen><userinput>make -f client.mk &amp;&amp;
make -C moz-build-dir/suite/installer</userinput></screen>
<screen><userinput>tar -xf ../enigmail-&seamonkey-enigmail-version;.tar.gz -C mailnews/extensions &amp;&amp;
( cd mailnews/extensions/enigmail &amp;&amp; ./makemake -r ) &amp;&amp;
make -C ../seamonkey-build/mailnews/extensions/enigmail &amp;&amp;
make -C ../seamonkey-build/mailnews/extensions/enigmail \
XPIFILE=enigmail-&seamonkey-enigmail-version;.xpi xpi</userinput></screen>
-->
<para>This package does not come with a test suite. However, it
can be launched from the build directory before installing with the
command line:
<userinput>../seamonkey-build/mozilla/dist/seamonkey/seamonkey</userinput>.</para>
<userinput>moz-build-dir/mozilla/dist/seamonkey/seamonkey</userinput></para>
<para>Install <application>SeaMonkey</application> by issuing the following
commands as the <systemitem class="username">root</systemitem> user:</para>
<screen role="root"><userinput>make -f client.mk install &amp;&amp;
install -v -m644 ../seamonkey-build/mozilla/dist/public/ldap-private/* \
/usr/include/seamonkey-&seamonkey-version;/ldap</userinput></screen>
<para>If you built <application>SeaMonkey</application> utilizing
system-installed NSS and NSPR libraries, the
<filename>seamonkey-ns*.pc</filename> <application>pkgconfig</application>
files are broken as they point to the wrong directories where the actual
libraries and interface headers are located. Issue the following commands
as the <systemitem class="username">root</systemitem> user to replace the
broken files with symbolic links to known good files:</para>
<screen role="root"><userinput>ln -v -sf nss.pc /usr/lib/pkgconfig/seamonkey-nss.pc &amp;&amp;
ln -v -sf nspr.pc /usr/lib/pkgconfig/seamonkey-nspr.pc</userinput></screen>
<para>If you did <emphasis role="strong">NOT</emphasis> build
<application>seamonkey</application> utilizing system-installed NSS and
NSPR libraries, issue the following commands as the
<systemitem class="username">root</systemitem> user to install the NSS
interface headers:</para>
<screen role="root"><userinput>install -v -m755 -d /usr/include/seamonkey-&seamonkey-version;/nss &amp;&amp;
cp -v -Lf ../seamonkey-build/mozilla/dist/{private,public}/nss/*.h \
/usr/include/seamonkey-&seamonkey-version;/nss</userinput></screen>
<!--
<para>If you built the <application>Enigmail</application> extension,
issue the following commands as the <systemitem
class="username">root</systemitem> user to install the
<filename>.xpi</filename> file into the
<filename class='directory'>/usr/lib/seamonkey-&seamonkey-version;/xpi_store</filename>
directory:</para>
<screen role="root"><userinput>install -v -m644 -D ../seamonkey-build/dist/bin/enigmail-&seamonkey-enigmail-version;.xpi \
/usr/lib/seamonkey-&seamonkey-version;/xpi_store/enigmail-&seamonkey-enigmail-version;.xpi</userinput></screen>
<para>There are two methods you can use to install the
<application>Enigmail</application> extension. Both are shown here and
provide similar functionality with one major difference. The first
method will install the extension system-wide and all users of SeaMonkey
will have an Enigmail-enabled mail client. The method shown later only
installs it on a per-user basis. The first method must be accomplished
now (before the object directory is removed) and uses the conventional
<command>make install</command> command to install the
<application>Enigmail</application> files straight from the distribution
directory of the object directory. The alternate method is shown as it
installs using the <filename class='extension'>.xpi</filename> file
created earlier and can be done later (at any time you desire) as the
file used to install <application>Enigmail</application> was copied into
<filename
class='directory'>/usr/lib/seamonkey-&seamonkey-version;/xpi_store</filename>
in the previous step. This method can be used to install any
downloaded <application>Mozilla</application> extension distributed in a
<filename class='extension'>.xpi</filename> file. There are many
extensions available for <application>SeaMonkey</application>. A list
containing many of them can be found at
<ulink url="http://extensionroom.mozdev.org/"/>.</para>
<para>If you want to install the <application>Enigmail</application>
extension now, which offers system-wide access, issue the following
command as the <systemitem class="username">root</systemitem> user:</para>
<screen role="root"><userinput>make -C ../seamonkey-build/mailnews/extensions/enigmail install</userinput></screen>
<para>To install an extension from a created or download
<filename class='extension'>.xpi</filename> file, you simply need to
<quote>open</quote> the <filename class='extension'>.xpi</filename> file
using the <quote>Open File</quote> option of the <quote>File</quote>
menu of the browser window. You can browse to find the file (for example,
the <application>Enigmail</application>
<filename class='extension'>.xpi</filename> file is located in
<filename
class='directory'>/usr/lib/seamonkey-&seamonkey-version;/xpi_store</filename>),
select it, then follow the prompts to install the extension.</para>
-->
<note>
<para>You should run <command>/usr/bin/seamonkey</command> once as the
<systemitem class="username">root</systemitem> user (or any user with
write privileges) to create some necessary additional files in the
<filename class='directory'>/usr</filename> hierarchy. Also do this
each time you install additional system-wide extensions.</para>
</note>
</sect2>
<sect2 role="commands" id="add-mozconfig"
xreflabel="Additional .mozconfig Options">
<title>Additional .mozconfig Options</title>
<para>Information about some of the additional options which can be added
to the <filename>.mozconfig</filename> configuration file is shown below.
Note that this is just a few of the options. You may wish to run
<command>./configure --help</command> and review each of the listed options
to discover what affect they have on the build. Feel free to add or remove
options to tailor the build to your desires. Listed below are some common
options not in the default <filename>.mozconfig</filename> file but can be
added in order to have the described effect on the SeaMonkey compile.</para>
<para><option>ac_add_options --enable-elf-dynstr-gc</option>: Removes
un-referenced strings from ELF shared objects generated during the build.
Note that this option breaks the build on alpha.</para>
<para><option>ac_add_options --disable-mailnews</option>: Disables the mail
and news clients.</para>
<para><option>ac_add_options --disable-ldap</option>: Disables LDAP support,
recommended if mail is disabled.</para>
<para><option>ac_add_options --enable-xterm-updates</option>: Displays the
current command in the <command>xterm</command> window title during the
compilation.</para>
<para><option>ac_add_options --enable-plaintext-editor-only</option>:
Disables support for HTML editing. Do not use this switch if you are
building the mail-news component.</para>
</sect2>
<sect2 role="commands">
<title>.mozconfig Option Explanations</title>
<para>To simplify reading the options below, they are labeled without
<parameter>ac_add_options</parameter> inserted at the beginning of the
option. These options are also described in the
<filename>.mozconfig</filename> file created earlier.</para>
<para><parameter>mk_add_options
MOZ_OBJDIR=@TOPSRCDIR@/../seamonkey-build</parameter>: Creates an object
directory and specifies to build the package in that directory. If desired,
modify the location of the object directory to a directory inside the
source tree by removing <quote>../</quote> from the line.</para>
<para><parameter>--enable-application=suite</parameter>: Identifies the
build as a <application>SeaMonkey</application> suite build.</para>
<para><parameter>--with-system-zlib --with-system-png
--with-system-jpeg --enable-system-cairo</parameter>: Uses the
system-installed versions of these packages.</para>
<para><parameter>--enable-xinerama --enable-reorder --enable-strip
--enable-cpp-rtti --disable-accessibility --disable-tests --disable-logging
--disable-pedantic --disable-installer</parameter>: Various options that
affect what components are built and some optimization options. You can
pick and choose from these options. More information on them, and many
other available options, can be found by running
<command>./configure --help</command>.</para>
<screen role="root"><userinput>mkdir -p /usr/lib/seamonkey-&seamonkey-version; &amp;&amp;
tar -xf moz-build-dir/mozilla/dist/seamonkey*.tar.bz2 \
-C /usr/lib/seamonkey-&seamonkey-version; --strip-components=1 &amp;&amp;
mkdir -p /usr/lib/mozilla/plugins &amp;&amp;
ln -s ../mozilla/plugins /usr/lib/seamonkey-&seamonkey-version; &amp;&amp;
ln -sf ../lib/seamonkey-&seamonkey-version;/seamonkey /usr/bin &amp;&amp;
cp moz-build-dir/mozilla/dist/man/man1/seamonkey.1 /usr/share/man/man1</userinput></screen>
</sect2>
<sect2 role="commands">
<title>Command Explanations</title>
<!--
<para><command>'EXTRA_DSO_LDOPTS' += -lX11 -lXrender ...</command>:
Building the layout backend will break when the canvas element is enabled
without adding these two required libraries.</para>
-->
<para><command>make -f client.mk ...</command>: Mozilla products are
<para><command>make -f client.mk</command>: Mozilla products are
packaged to allow the use of a configuration file which can be used to
pass the configuration settings to the <command>configure</command>
command. <command>make</command> uses the <filename>client.mk</filename>
file to get initial configuration and setup parameters, then depending on
the target parameter (<parameter>build</parameter> or
<parameter>install</parameter>), either runs the
<command>configure</command> script and compiles the package or installs
the package.</para>
<!--
<para><command>./makemake -r</command>: This command is used to recursively
create <filename>Makefile</filename>s in the appropriate subdirectory
of <filename class='directory'>seamonkey-build</filename>.</para>
file to get initial configuration and setup parameters.</para>
<para><command>make -C ... xpi</command>: This command builds the
<application>Enigmail</application>
<filename class='extension'>.xpi</filename> file which can be used to
install <application>Enigmail</application>.</para>
<para><command>make -C moz-build-dir/suite/installer</command>: this
creates a tarball of the <application>Seamonkey</application> you've just
compiled.</para>
<para><command>tar -xf moz-build-dir ...</command>: this untars
<application>Seamonkey</application>. The <option>-C
/usr/lib/seamonkey-2.5</option> tells tar to change to the <filename
class='directory'>/usr/lib/seamonkey-2.5</filename> directory before
untaring it. The <option>--strip-components=1</option> option removes the
leading seamonkey/ from the filename/paths.</para>
<para><command>ln -s ../mozilla/plugins /usr/lib/seamonkey-2.5</command>:
this creates a symlink to
<filename class='directory'>/usr/lib/mozilla/plugins</filename> for the
sake of compatibility, to keep all your plugins in the place mozilla
plugins are normally found.</para>
<para><command>install .../movemail.rdf ...</command>: This
command is used to install a file inadvertently left out of the
installation script.</para>
-->
</sect2>
<sect2 role="configuration">
<title>Configuring SeaMonkey</title>
<para>No specific configuration is required as long as the
<command>seamonkey</command> script is in the user's path. If
<application>SeaMonkey</application> is installed in a non-standard location,
make a symlink to the <command>seamonkey</command> script in the
<filename class="directory">/usr/bin</filename> directory.</para>
<para>Some applications look for <command>netscape</command> when they need
to open a browser. You may make the following symlink for convenience (as
the <systemitem class="username">root</systemitem> user).</para>
<screen role="root"><userinput>ln -v -sf seamonkey /usr/bin/netscape</userinput></screen>
<para>If you deleted the <option>--disable-webm</option> option from your
<filename>mozconfig</filename>, your <application>Seamonkey</application>
can play most youtube videos without the need for the flash plugin. To
enable this, go to <ulink
url="http://www.youtube.com/html5">http://www.youtube.com/html5</ulink>
and click on &apos;Join the HTML5 Trial&apos; (needs cookies
enabled).</para>
<para>For installing various <application>SeaMonkey</application> plugins,
refer to <ulink url="http://plugindoc.mozdev.org/linux.html">Mozdev's
PluginDoc Project</ulink>. If you have <xref linkend="jdk"/> already
installed, create the following link as the
<systemitem class="username">root</systemitem> user to utilize the
<application>JAVA</application> plugin: </para>
<screen role="root"><userinput>ln -v -s $JAVA_HOME/jre/plugin/i386/ns7/libjavaplugin_oji.so \
/usr/lib/seamonkey-&seamonkey-version;/plugins</userinput></screen>
<para>If you have <xref linkend="icedtea6"/> installed as opposed to the
<xref linkend="jdk"/>, create the following link (again as the
<systemitem class="username">root</systemitem> user) to use the
<application>IcedTea6</application> plugin: </para>
<screen role="root"><userinput>ln -v -s $JAVA_HOME/jre/plugin/i386/IcedTeaPlugin.so \
/usr/lib/seamonkey-&seamonkey-version;/plugins</userinput></screen>
<para>Some packages install SeaMonkey plugins into the default system-wide
directory <filename class='directory'>/usr/lib/mozilla/plugins</filename>.
If desired, create symbolic links in the <application>SeaMonkey</application>
plugin directory
<filename class='directory'>/usr/lib/seamonkey-&seamonkey-version;/plugins</filename>
to the files in the default plugin directory (you should link to the actual
files and not other links). Alternatively, you can move or copy the files
in the default plugin directory to the
<application>SeaMonkey</application> plugin directory. An example of creating
a symbolic link is shown below. Create the links as the
<systemitem class="username">root</systemitem> user:</para>
<screen role="root"><userinput>ln -v -s ../../mozilla/plugins/<replaceable>&lt;plugin.so&gt;</replaceable> \
/usr/lib/seamonkey-&seamonkey-version;/plugins</userinput></screen>
PluginDoc Project</ulink>.</para>
<para>Along with using the <quote>Preferences</quote> menu to configure
<application>SeaMonkey</application>'s options and preferences to suit
@ -530,13 +262,11 @@ cp -v -Lf ../seamonkey-build/mozilla/dist/{private,public}/nss/*.h \
<segtitle>Installed Directories</segtitle>
<seglistitem>
<seg>seamonkey and seamonkey-config</seg>
<seg>seamonkey</seg>
<seg>Numerous libraries, browser, and email/newsgroup components,
plugins, extensions, and helper modules installed in <filename
class='directory'>/usr/lib/seamonkey-&seamonkey-version;</filename></seg>
<seg>/usr/include/seamonkey-&seamonkey-version;,
/usr/lib/seamonkey-&seamonkey-version;, and
/usr/share/idl/seamonkey-&seamonkey-version;</seg>
<seg>/usr/lib/seamonkey-&seamonkey-version;</seg>
</seglistitem>
</segmentedlist>