r5690 - trunk/BOOK/xsoft/graphweb

randy at linuxfromscratch.org randy at linuxfromscratch.org
Tue Feb 28 07:30:15 PST 2006


Author: randy
Date: 2006-02-28 08:30:14 -0700 (Tue, 28 Feb 2006)
New Revision: 5690

Modified:
   trunk/BOOK/xsoft/graphweb/seamonkey.xml
Log:
Updated some of the SeaMonkey instructions

Modified: trunk/BOOK/xsoft/graphweb/seamonkey.xml
===================================================================
--- trunk/BOOK/xsoft/graphweb/seamonkey.xml	2006-02-27 21:02:33 UTC (rev 5689)
+++ trunk/BOOK/xsoft/graphweb/seamonkey.xml	2006-02-28 15:30:14 UTC (rev 5690)
@@ -11,36 +11,12 @@
   <!ENTITY mozilla-buildsize          "625 MB">
   <!ENTITY mozilla-time               "15.3 SBU">
 
-  <!--
-
-  BLFS Devs:
-
-  The information below is for the Enigmail and IPC downloads. Additionally,
-  a makemake file is download because we cannot build Enigmail using an
-  object directory without it. Information about the Enigmail source to
-  check for updates is located at http://enigmail.mozdev.org/source.html.
-
-  The link to the makemake file is near the end of the page in the section
-  titled "Using OBJDIR when building Enigmail". Ensure you check the rev
-  level of the link and update the "enigmail-makemake-version" entitity
-  if necessary. In case you are wondering why the version has the question
-  mark and "rev=" in it, it is because the complete URL is used in a command
-  and it would extend past the 71 characters that PDF render is limited to.
-  It should make sense after you see it rendered in the wget command.
-
-  -->
-
   <!ENTITY mozilla-enigmail-version   "0.94.0">
-  <!ENTITY mozilla-ipc-version        "1.1.3">
-  <!ENTITY enigmail-makemake-version  "?rev=1.3">
   <!ENTITY mozilla-enigmail-download  "http://www.mozilla-enigmail.org/downloads/src/enigmail-&mozilla-enigmail-version;.tar.gz">
-  <!ENTITY mozilla-ipc-download       "http://www.mozilla-enigmail.org/downloads/src/ipc-&mozilla-ipc-version;.tar.gz">
-  <!ENTITY enigmail-makemake-download "http://www.mozdev.org/source/browse/~checkout~/enigmail/src/makemake">
   <!ENTITY mozilla-enigmail-md5sum    "d326c302c1d2d68217fffcaa01ca7632">
-  <!ENTITY mozilla-ipc-md5sum         "64ba4c6e3b52568468c4f6680ec7e679">
 ]>
 
-<sect1 id="seamonkey" xreflabel="Seamonkey-&seamonkey-version;">
+<sect1 id="seamonkey" xreflabel="SeaMonkey-&seamonkey-version;">
   <?dbhtml filename="seamonkey.html" ?>
 
   <sect1info>
@@ -52,16 +28,16 @@
     </keywordset>
   </sect1info>
 
-  <title>Seamonkey-&seamonkey-version;</title>
+  <title>SeaMonkey-&seamonkey-version;</title>
 
   <indexterm zone="seamonkey">
-    <primary sortas="a-Seamonkey">Seamonkey</primary>
+    <primary sortas="a-SeaMonkey">SeaMonkey</primary>
   </indexterm>
 
   <sect2 role="package">
-    <title>Introduction to Seamonkey</title>
+    <title>Introduction to SeaMonkey</title>
 
-    <para><application>Seamonkey</application> is a browser suite, the Open
+    <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, a calendar client and an
     IRC client.  It is the follow-on to the Mozilla browser suite.</para>
@@ -106,26 +82,22 @@
         <para>Estimated build time: &mozilla-time;</para>
       </listitem>
     </itemizedlist>
-<!--
+
     <bridgehead renderas="sect3">Additional Downloads</bridgehead>
     <itemizedlist spacing="compact">
       <listitem>
-        <para>Required patch:
-        <ulink
-        url="&patch-root;/mozilla-&mozilla-version;-system_nss-1.patch"/>
-         (if using system-installed versions of <application>NSS</application> 
-         and <application>NSPR</application>)
+        <para>Required patch (if using system-wide NSS/NSPR provided by
+        <xref linkend="nss"/>): <ulink
+        url="&patch-root;/seamonkey-&seamonkey-version;-system_nss-1.patch"/>
         </para>
       </listitem>
     </itemizedlist>
--->
 
     <para>To enable the <application>Enigmail</application> extension to the
-    <application>Seamonkey</application> mail client, you'll need to download
-    the two tarballs and <command>makemake</command> file 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>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"/> installed.</para>
 
@@ -136,31 +108,10 @@
       <listitem>
         <para>Download MD5 sum (Enigmail): &mozilla-enigmail-md5sum;</para>
       </listitem>
-      <listitem>
-        <para><ulink url="&mozilla-ipc-download;"/></para>
-      </listitem>
-      <listitem>
-        <para>Download MD5 sum (IPC): &mozilla-ipc-md5sum;</para>
-      </listitem>
-      <listitem>
-        <para><ulink
-        url="&enigmail-makemake-download;&enigmail-makemake-version;"/></para>
-      </listitem>
     </itemizedlist>
 
-    <para>The <command>makemake</command> file is an enhanced version that will
-    be copied into the source tree to replace an existing file during the
-    installation instructions. The instructions expect the file to be named
-    <filename>seamonkey-&seamonkey-version;-enigmail_makemake</filename>. If you
-    have <xref linkend="wget"/> installed, you can download and rename the file
-    in one step using the following command:</para>
+    <bridgehead renderas="sect3">SeaMonkey Dependencies</bridgehead>
 
-<screen><userinput>wget -O seamonkey-&seamonkey-version;-enigmail_makemake \
-&enigmail-makemake-download;\
-&enigmail-makemake-version;</userinput></screen>
-
-    <bridgehead renderas="sect3">Seamonkey Dependencies</bridgehead>
-
     <bridgehead renderas="sect4">Required</bridgehead>
     <para role="required">
       <xref linkend="gtk2"/>,
@@ -169,8 +120,8 @@
     </para>
 
     <note>
-      <para><application>libjpeg</application> should have been installed
-      before <application>GTK+</application> and should exist on your system. If
+      <para><xref linkend="libjpeg"/> should have been installed before
+      <application>GTK+</application> and should exist on your system. If
       for some reason you haven't installed <application>libjpeg</application>,
       you should remove the <option>--with-system-jpeg</option> option from the
       <filename>.mozconfig</filename> file created below.</para>
@@ -178,27 +129,24 @@
 
     <bridgehead renderas="sect4">Recommended</bridgehead>
     <para role="recommended">
-      <xref linkend="nss"/> (needed if you will be installing any other 
-      package that utilizes NSS/NSPR, such as <application>Firefox</application>, 
+      <xref linkend="nss"/> (if you will be installing any other package that
+      utilizes NSS/NSPR, such as <application>Firefox</application>,
       <application>Thunderbird</application> or 
       <application>Evolution</application>)
     </para>
 
     <bridgehead renderas="sect4">Optional</bridgehead>
     <para role="optional">
-      <xref linkend="unzip"/>,
-      <xref linkend="gnome-vfs"/> (to build the gnomevfs extension),
-      <xref linkend="libart_lgpl"/>, and
-      <xref linkend="heimdal"/> or <xref linkend="mitkrb"/>
-      (for the GSSAPI libraries to build the negotiateauth extension)
+      <xref linkend="unzip"/> and
+      <xref linkend="libgnomeui"/> (to build the gnomevfs extension)
     </para>
 
   </sect2>
 
   <sect2 role="installation">
-    <title>Installation of Seamonkey</title>
+    <title>Installation of SeaMonkey</title>
 
-    <para>The configuration of <application>Seamonkey</application> is
+    <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>
     file is created below. To see the entire list of available configuration
@@ -207,7 +155,7 @@
     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 at the bottom of the file. If
+    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"/>
@@ -217,79 +165,126 @@
     command:</para>
 
 <screen><userinput>cat > .mozconfig << "EOF"
-<literal># Options for client.mk
+<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'.
 
-mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/../mozilla-build
 
-# Options for 'configure' (same as command-line options)
+# 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
 
-# Mandatory options
+# This option is used to specify that the SeaMonkey suite is
+# being built and to use all the default options for SeaMonkey.
 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
 
-# Options for system-installed software
+# 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-system-cairo
 
-# Options in all Mozilla-family builds
+# This option specifies to include support for rendering the HTML
+# <canvas></canvas> 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 --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
 
-# Options used just for Mozilla/Seamonkey Suite
+# 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
+
+# This option is used to enable the calendar program in the
+# SeaMonkey suite.
 ac_add_options --enable-calendar
 
-# Options used for system-installed NSS/NSPR
+# 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</literal>
+#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
+
+# 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-1.0</literal>
+
 EOF</userinput></screen>
-<!--
+
     <para>If you have system-installed Network Security Services (NSS) and
     Netscape Portable Runtime (NSPR) libraries and you uncommented the
     appropriate lines in the <filename>.mozconfig</filename> file to utilize
     them, apply the following patch:</para>
 
 <screen><userinput>patch -Np1 -i ../seamonkey-&seamonkey-version;-system_nss-1.patch</userinput></screen>
--->
-    <para>Compile <application>Seamonkey</application> by running the
-    following commands:</para>
 
+    <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>
+    <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>tar -xf ../enigmail-&mozilla-enigmail-version;.tar.gz -C mailnews/extensions &&
-tar -xf ../ipc-&mozilla-ipc-version;.tar.gz -C extensions &&
 
-install -v -m755 -b ../seamonkey-&mozilla-version;-enigmail_makemake \
-    extensions/ipc/makemake &&
-install -v -m755 -b ../seamonkey-&mozilla-version;-enigmail_makemake \
-    mailnews/extensions/enigmail/makemake &&
-
-cd extensions/ipc &&
+pushd mailnews/extensions/enigmail &&
 ./makemake -r &&
+popd &&
 
-cd ../../mailnews/extensions/enigmail &&
-./makemake -r &&
+make -C ../seamonkey-build/mailnews/extensions/enigmail &&
+make -C ../seamonkey-build/mailnews/extensions/enigmail xpi</userinput></screen>
 
-cd ../../.. &&
-make -C ../mozilla-build/extensions/ipc &&
-make -C ../mozilla-build/mailnews/extensions/enigmail &&
-make -C ../mozilla-build/mailnews/extensions/enigmail xpi</userinput></screen>
-
-    <para>Install <application>Seamonkey</application> by issuing the following
+    <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 &&
 
-install -v -m644 ../mozilla-build/dist/public/ldap-private/* \
+install -v -m644 ../seamonkey-build/dist/public/ldap-private/* \
     /usr/include/seamonkey-&seamonkey-version;/ldap &&
 
 install -v -m755 -d /usr/lib/seamonkey-&seamonkey-version;/defaults/isp/US &&
@@ -297,34 +292,7 @@
     /usr/lib/seamonkey-&seamonkey-version;/defaults/isp &&
 ln -v -s ../movemail.rdf /usr/lib/seamonkey-&seamonkey-version;/defaults/isp/US</userinput></screen>
 
-<!-- Commenting this out per the discussion on BLFS-Dev about this.
-     The stuff commented out below is replaced with text in the
-     Configuration section to create links to any system-wide 
-     plugins the user may have installed
-
-if [ -L /usr/lib/mozilla/plugins ]; then
-     rm /usr/lib/mozilla/plugins
-fi &&
-if [ -L /usr/lib/mozilla ]; then
-     rm /usr/lib/mozilla
-fi &&
-
-install -v -m755 -d /usr/lib/mozilla/plugins &&
-cp -v /usr/lib/mozilla-1.7.12/plugins/* /usr/lib/mozilla/plugins &&
-rm -f /usr/lib/mozilla-1.7.12/plugins &&
-ln -v -s ../mozilla/plugins /usr/lib/mozilla-1.7.12 &&
--->
-
-<!-- The following commented out per the discussion on BLFS-Dev. It
-     has been determined that we will no longer continue to support
-     broken programs that don't look at pkgconfig files to find out
-     where Mozilla is installed
-
-ln -v -nsf mozilla-&mozilla-version; /usr/include/mozilla &&
-ln -v -nsf mozilla-&mozilla-version; /usr/lib/mozilla &&
--->
-
-    <para>If you built <application>Seamonkey</application> utilizing
+    <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
@@ -342,7 +310,7 @@
     interface headers:</para>
 
 <screen role="root"><userinput>install -v -m755 -d /usr/include/seamonkey-&seamonkey-version;/nss &&
-cp -v -Lf ../mozilla-build/dist/{private,public}/nss/*.h \
+cp -v -Lf ../seamonkey-build/dist/{private,public}/nss/*.h \
    /usr/include/seamonkey-&seamonkey-version;/nss</userinput></screen>
 
     <para>If you built the <application>Enigmail</application> extension,
@@ -353,16 +321,19 @@
     directory:</para>
 
 <screen role="root"><userinput>install -v -m755 -d /usr/lib/seamonkey-&seamonkey-version;/xpi_store &&
-install -v -m644 ../mozilla-build/dist/bin/enigmail-&mozilla-enigmail-version;-*.xpi \
+install -v -m644 ../seamonkey-build/dist/bin/enigmail-&mozilla-enigmail-version;-*.xpi \
     /usr/lib/seamonkey-&seamonkey-version;/xpi_store</userinput></screen>
 
       <para>There are two methods you can use to install the
       <application>Enigmail</application> extension. Both are shown here and
-      provide the same functionality. The first method must be accomplished
+      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. An alternate method is shown as it
+      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
@@ -371,75 +342,33 @@
       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
+      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, issue the following commands as the
-    <systemitem class="username">root</systemitem> user:</para>
+    extension now, which offers system-wide access, issue the following
+    commands as the <systemitem class="username">root</systemitem> user:</para>
 
-<screen role="root"><userinput>make -C ../mozilla-build/extensions/ipc install &&
-make -C ../mozilla-build/mailnews/extensions/enigmail install</userinput></screen>
+<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 Navigator window. You can browse to find the file (for example,
+    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>
 
-    <!-- Commenting this out as there really is no need to put the Mozilla
-         Suite versions of NSS/NSPR in a system-wide location when there
-         is now a BLFS package that does this.
-
-    <para>Some libraries, including the Netscape Portable Runtime (NSPR) and
-    Network Security Services (NSS) libraries, installed by
-    <application>Mozilla</application> are also needed by other packages.
-    These libraries should be in <filename class="directory">/usr/lib</filename>
-    so that other packages can link against them. As the <systemitem
-    class="username">root</systemitem> user, move them as follows:</para>
-
-<screen role="root"><userinput>for i in \
-    lib{nspr4,plc4,plds4,nss3,smime3,softokn3,ssl3}.so libsoftokn3.chk
-do
-   mv -v /usr/lib/mozilla-&mozilla-version;/$i /usr/lib/
-   ln -v -sf ../$i /usr/lib/mozilla-&mozilla-version;/
-done</userinput></screen>
-
-    -->
-
-    <!-- Commenting this out for now, as I believe this is only necessary
-         for the binary versions of Mozilla. I've built this and had many
-         system users access Mozilla simultaneously without having to do
-         the steps shown here.
-
-    <para>Create the required component registries to enable multi-user
-    installs. These steps should be preformed by the <systemitem
-    class="username">root</systemitem> user each time a
-    <application>Mozilla</application> add-on is installed. This will allow
-    unprivileged users to run <command>mozilla</command>. Enable multi-user
-    operation by executing the following:</para>
-
-<screen role="root"><userinput>cd /usr/lib/mozilla-&mozilla-version; &&
-export LD_LIBRARY_PATH="$PWD" &&
-export MOZILLA_FIVE_HOME="$PWD" &&
-./regxpcom &&
-./regchrome &&
-touch `find . -name *.rdf`</userinput></screen>
-
-    -->
-
     <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 extensions.</para>
+      each time you install additional system-wide extensions.</para>
     </note>
 
   </sect2>
@@ -456,7 +385,7 @@
     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>
+    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.
@@ -483,48 +412,32 @@
 
     <para>To simplify reading the options below, they are labeled without
     <parameter>ac_add_options</parameter> inserted at the beginning of the
-    option.</para>
+    option. These options are also described in the
+    <filename>.mozconfig</filename> file created earlier.</para>
 
     <para><parameter>mk_add_options
-    MOZ_OBJDIR=@TOPSRCDIR@/../mozilla-build</parameter>: Creates an object
+    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>
+    build as a <application>SeaMonkey</application> suite build.</para>
 
     <para><parameter>--with-system-zlib --with-system-png
-    --with-system-jpeg</parameter>: Uses the system-installed versions of these
-    packages.</para>
+    --with-system-jpeg --enable-system-cairo</parameter>: Uses the
+    system-installed versions of these packages.</para>
 
-    <para><parameter>--enable-default-toolkit=gtk2 --enable-xft 
-    --disable-freetype2</parameter>: Use the GTK2 toolkit for graphics
-    rendering and XFT (automatically pulls in the
-    <application>FreeType</application> libraries) for font rendering.</para>
-
-    <para><parameter>--enable-extensions=all</parameter>: Enables all available
-    extensions. If you want, you can disable any or all extensions other than
-    the browser by changing this switch to
-    <option>--enable-extensions="default,-venkman,-inspector,..."</option>.
-    For a short description of the various extensions available with the
-    <application>Seamonkey</application> source, see <ulink
-    url="http://linuxfromscratch.org/~tushar/downloads/mozilla-extensions.txt"/>.
-    </para>
-
-    <para><parameter>--enable-crypto</parameter>: Enable the Personal
-    Security Manager to enable SSL connections.</para>
-
     <para><parameter>--enable-calendar</parameter>: Builds the calendar
     application. Remove this parameter if you don't wish to build it.</para>
 
-    <para><parameter>--enable-xinerama; --enable-optimize; --enable-reorder;
-    --enable-strip; --enable-cpp-rtti --disable-accessibility; --disable-debug;
-    --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>
+    <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>
 
   </sect2>
 
@@ -543,7 +456,7 @@
 
     <para><command>./makemake -r</command>: This command is used to recursively
     create <filename>Makefile</filename>s in the appropriate subdirectory
-    of mozilla-build.</para>
+    of seamonkey-build.</para>
 
     <para><command>make -C ... xpi</command>: This command builds the
     <application>Enigmail</application>
@@ -554,32 +467,14 @@
     command is used to install a file inadvertently left out of the
     installation script.</para>
 
-    <!-- Commenting this out as the commands needing these explanations
-         are also commented out
-
-    <para><command>if [ -d /usr/lib/mozilla/plugins ] ... fi</command>: Some
-    applications may have already installed <application>Mozilla</application>
-    plugins. This set of commands moves any existing plugins to the newly
-    created plugin directory, then removes the existing
-    <filename class='directory'>/usr/lib/mozilla</filename> directory.</para>
-
-    <para><command>ln -nsf mozilla-&mozilla-version; ...</command>:
-    <application>Mozilla</application> installs headers and libraries in
-    version specific directories. These commands makes symbolic links so that
-    applications depending on <application>Mozilla</application> (such as
-    <application>OpenOffice</application>, <application>Galeon</application>,
-    etc.) don't need to know which version of <application>Mozilla</application>
-    is installed.</para>
-    -->
-
   </sect2>
 
   <sect2 role="configuration">
-    <title>Configuring Seamonkey</title>
+    <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,
+    <application>SeaMonkey</application> is installed in a non-standard location,
     then make a symlink to the <command>seamonkey</command> script in the
     <filename class="directory">/usr/bin</filename> directory.</para>
 
@@ -589,7 +484,7 @@
 
 <screen role="root"><userinput>ln -v -sf seamonkey /usr/bin/netscape</userinput></screen>
 
-    <para>For installing various <application>Seamonkey</application> plugins,
+    <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
@@ -599,15 +494,15 @@
 <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>Some packages install Seamonkey plugins into the default system-wide
+    <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>
+    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
+    <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>
 
@@ -615,10 +510,10 @@
     /usr/lib/seamonkey-&seamonkey-version;/plugins</userinput></screen>
 
     <para>Along with using the <quote>Preferences</quote> menu to configure
-    <application>Seamonkey</application>'s options and preferences to suit
+    <application>SeaMonkey</application>'s options and preferences to suit
     individual tastes, finer grain control of many options is only available
     using a tool not available from the general menu system. To access this
-    tool, you'll need to open a Navigator window and enter
+    tool, you'll need to open a browser window and enter
     <systemitem role='url'>about:config</systemitem> in the
     address bar. This will display a list of the configuration preferences and
     information related to each one. You can use the <quote>Filter:</quote> bar
@@ -633,7 +528,7 @@
 
     <tip>
       <para>There is a multitude of configuration parameters you can tweak to
-      customize <application>Seamonkey</application>. A very extensive and
+      customize <application>SeaMonkey</application>. A very extensive and
       up-to-date list of these parameters can be found at <ulink
       url="http://preferential.mozdev.org/preferences.html"/>.</para>
     </tip>




More information about the blfs-book mailing list