[jhbuild] [doc] Remove FAQ from manual, to be added to wiki (GNOME bug 624079)

[Craig Keogh <cskeogh src gnome org>]

commit f5c29016b54a55b610745ec058f2565a42f7132f
Author: Craig Keogh <cskeogh adam com au>
Date:   Sun Jul 11 11:59:12 2010 +0930

    [doc] Remove FAQ from manual, to be added to wiki (GNOME bug 624079)
    
    FAQ to be added to wiki at http://live.gnome.org/Jhbuild

 doc/C/jhbuild.xml |  148 -----------------------------------------------------
 1 files changed, 0 insertions(+), 148 deletions(-)
---
diff --git a/doc/C/jhbuild.xml b/doc/C/jhbuild.xml
index fbad474..5a2e41d 100644
--- a/doc/C/jhbuild.xml
+++ b/doc/C/jhbuild.xml
@@ -3070,152 +3070,4 @@ libgnomecanvas is missing branch definition for gnome-2-20
       </section> <!-- end of deprecated module types -->
     </section> <!-- end of deprecated elements -->
   </section>
-
-  <section id="faq">
-    <title>Frequently Asked Questions</title>
-
-    <qandaset defaultlabel="qanda">
-      <qandadiv>
-	<title>General JHBuild Questions</title>
-	<qandaentry>
-	  <question>
-	    <simpara>The <command>wget</command> command can't
-	    download any tarballs.  How do I get it to work with my
-	    firewall?</simpara>
-	  </question>
-	  <answer>
-	    <para>Create <filename>~/.wgetrc</filename> file.  If an HTTP
-        proxy is used to access FTP sites, add a line like
-	    the following to the file:</para>
-	    <programlisting>ftp_proxy = http://<replaceable>hostname</replaceable>:<replaceable>port</replaceable>/</programlisting>
-	    <para>If passive FTP connections are required
-	    (sometimes needed with NAT firewalls), add the following
-	    line:</para>
-	    <programlisting>passive_ftp = on</programlisting>
-	  </answer>
-	</qandaentry>
-	<qandaentry>
-	  <question>
-	    <simpara>Building is slow.  Is there any way I can
-	    speed it up?</simpara>
-	  </question>
-	  <answer>
-	    <para><ulink url="http://ccache.samba.org/";>CCache</ulink>
-        can speed up compilations, as it caches compilation results.
-        <command>CCache</command> is available with most distributions.
-        </para>
-	    <para>Set the cache size with the following command:</para>
-	    <programlisting>ccache -M 2G</programlisting>
-	    <para>(where <literal>2G</literal> is the size the cache).
-        Create symlinks to <command>CCache</command> for
-	    the compiler in <filename>~/bin</filename>:</para>
-	    <programlisting>cd ~/bin
-for cmd in cc gcc c++ g++; do
-  ln -s /usr/bin/ccache $cmd
-done</programlisting>
-            <para>It is possible to check the status of the cache
-            including cache hit rates with the following command:</para>
-	    <programlisting>ccache -s</programlisting>
-	  </answer>
-	</qandaentry>
-	<qandaentry>
-	  <question>
-	    <simpara>Is there a better way to monitor the status of
-	    the build than looking at terminal window?</simpara>
-	  </question>
-	  <answer>
-	    <para>If Zenity >= 2.9 is installed on your system,
-	    JHBuild will display an icon in the system tray.  The icon
-	    will display the current build stage, and the tooltip will
-	    show the last message from JHBuild.</para>
-	    <para>The icon will also pop up a balloon on error.</para>
-	  </answer>
-	</qandaentry>
-      </qandadiv>
-      <qandadiv>
-	<title>Building GNOME</title>
-	<qandaentry>
-	  <question>
-	    <simpara>What other prerequisites are needed to build GNOME
-	    with JHBuild?</simpara>
-	  </question>
-	  <answer>
-	    <para>Some of the packages required include:</para>
-	    <itemizedlist>
-	      <listitem>
-		<simpara>DocBook XML DTD and XSLT stylesheets.  These
-		need to be registered in the XML catalog
-		(<filename>/etc/xml/catalog</filename>).</simpara>
-	      </listitem>
-	      <listitem>
-		<simpara>X libraries</simpara>
-	      </listitem>
-	      <listitem>
-		<simpara>fam or gamin (used by gnome-vfs for file
-		monitoring).</simpara>
-	      </listitem>
-	      <listitem>
-		<simpara><filename>libsmbclient</filename> from Samba
-		(used for browsing Windows networks).</simpara>
-	      </listitem>
-	      <listitem>
-	      <simpara><filename>libbz2</filename> from
-		bzip2.</simpara>
-	      </listitem>
-	      <listitem>
-		<simpara><filename>libpng</filename>,
-		<filename>libjpeg</filename> and
-		<filename>libtiff</filename> (used for image
-		loading).</simpara>
-	      </listitem>
-	    </itemizedlist>
-	    <para>If installing distribution packages, and if applicable
-        for your distribution, install the corresponding
-        <quote>dev</quote> or <quote>devel</quote> packages.  A list of
-	    <ulink url="http://live.gnome.org/JhbuildDependencies";>package
-	    names</ulink> for different distributions is maintained on the
-	    GNOME wiki.</para>
-	  </answer>
-	</qandaentry>
-	<qandaentry>
-	  <question>
-	    <simpara>I built GNOME using JHBuild with
-	    <varname>prefix</varname> set to <filename>/usr</filename>,
-	    and now my system is broken.  What should I do?</simpara>
-	  </question>
-	  <answer>
-	    <para>Don't set <varname>prefix</varname> to
-	    <filename>/usr</filename>.</para>
-	  </answer>
-	</qandaentry>
-	<qandaentry>
-	  <question>
-	    <simpara>How do I get
-	    <command>gnome-volume-manager</command> to work when
-	    running JHBuild GNOME?</simpara>
-	  </question>
-	  <answer>
-	    <para>The <command>gnome-volume-manager</command> program
-	    reacts to messages from <command>hald</command> over the
-	    system message bus, which must be running as root.
-	    Assuming that your distribution comes with
-	    <acronym>HAL</acronym>, the main problem is getting
-	    <command>gnome-volume-manager</command> to talk to the
-	    system message bus.</para>
-	    <para>As communication is over a UNIX domain
-	    socket, the easiest way is to create a symlink
-	    from <filename>/var/run/dbus</filename> to
-	    <filename>$prefix/var/run/dbus</filename>:</para>
-	    <programlisting>mkdir -p $prefix/var/run
-cd $prefix/var/run
-ln -s /var/run/dbus dbus</programlisting>
-        <para>You may also have trouble building HAL with JHBuild,
-        since it tries to install some things outside of its build
-        root.  Running <userinput>make -k install</userinput> in
-        the hal directory might help here.</para>
-	  </answer>
-	</qandaentry>
-      </qandadiv>
-    </qandaset>
-  </section>
 </article>