gnash-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gnash-commit] gnash/doc/C/usermanual installation.xml


From: Melissa Goldin
Subject: [Gnash-commit] gnash/doc/C/usermanual installation.xml
Date: Thu, 16 Aug 2007 14:19:19 +0000

CVSROOT:        /sources/gnash
Module name:    gnash
Changes by:     Melissa Goldin <mushi>  07/08/16 14:19:19

Modified files:
        doc/C/usermanual: installation.xml 

Log message:
        Added a bit more explanatory text.

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/usermanual/installation.xml?cvsroot=gnash&r1=1.4&r2=1.5

Patches:
Index: installation.xml
===================================================================
RCS file: /sources/gnash/gnash/doc/C/usermanual/installation.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- installation.xml    1 Aug 2007 04:58:21 -0000       1.4
+++ installation.xml    16 Aug 2007 14:19:19 -0000      1.5
@@ -14,31 +14,11 @@
 Before downloading and installing &app;, check that your hardware and software 
meet the following requirements.
 </para>
 
-<sect2 id="software">
-<title>Software Requirements</title>
-
-<para>
-The 0.8.0 release of &app; has been designed to run on UNIX/Linux variants, 
and has been run on most of the free ones.  However, &app; hassucessfully run 
on Windows, Darwin (Mac OS X), Iris, Solaris, BeOs, OS/2, and Haiku.  &app; has 
also run on the following 64-bit systems: PowerPC, Itanium, UltraSparc, and 
AMD64.   For now, it is important to be sure that the following code, testing, 
and documentation dependencies are met before installing &app;.  If you will be 
downloading &app; with a package manager, these dependencies may be solved by 
the pacakge manager.  Otherwise, you must first verify that each of these 
dependencies are installed on the target system.
-</para>
-
- <sect3 id="codedepend">
-       &codedependencies;
-    </sect3>
-
- <sect3 id="testdepend">
-       &testdependencies;
-    </sect3>
-
-<sect3 id="docdepend">
-       &docdependencies;
-    </sect3>
-</sect2>
-
 <sect2 id="hardware">
 <title>Hardware Requirements</title>
 
 <para>
-One of the goals of &app; is to make it portable enough to install on small 
devices.  As a result, the hardware requirements are minimal. &app; has even 
run on an ARM9 at 200 MHz with 64 MB of RAM ! (It ran without video support in 
this case.)   While firm minimums have not been established, &app; has been 
shown to run successfully with the following:
+One of the goals of &app; is to make it portable enough to install on small 
devices.  As a result, the hardware requirements are minimal. &app; has even 
run on an ARM9 at 200 MHz with 64 MB of RAM! (It ran without video support in 
this case.)   While firm minimums have not been established, &app; has been 
shown to run successfully with the following:
 </para>
 
 <itemizedlist>
@@ -58,6 +38,160 @@
 </para>
 </listitem>
 </itemizedlist>
+
+<para>
+The following table provides a list of the Operating System/CPU combinations 
on which &app; has been shown to run.
+</para>
+
+<table id="tb-os-cpu">
+<title>Build Matrix</title>
+<tgroup cols='2' align='left' colsep='1' rowsep='1'>
+<colspec colname='Operating System' />
+<colspec colname='CPU' />
+<thead>
+<row>
+  <entry>Render GUI</entry>
+  <entry>Virtual Memory</entry>
+</row>
+</thead>
+<tbody>
+<row>
+<entry>FreeBSD</entry>
+<entry>Alpha AXP, AMD64, i386, Itanium, PC-98, PowerPC, SPARC64 
+</entry>
+</row>
+<row>
+<entry>GNU/Linux 
+</entry>
+<entry>CRIS</entry>
+</row>
+<row>
+<entry>GNU/Linux [OLPC] 
+</entry>
+<entry>Geode GX 
+</entry>
+</row>
+<row>
+<entry>GNU/Linux ALTLinux 
+</entry>
+<entry>i586</entry>
+</row>
+<row>
+<entry>GNU/Linux Arklinux 
+</entry>
+<entry>i586</entry>
+</row>
+<row>
+<entry>GNU/Linux Debian 
+</entry>
+<entry>Alpha AXP, AMD64, ARM, hppa, i386, Itanium, MIPS, PowerPC, IBM zSeries 
(s390), SPARC 
+</entry>
+</row>
+<row>
+<entry>GNU/Linux Fedora core 
+</entry>
+<entry>x86-32, x86-64 
+</entry>
+</row>
+<row>
+<entry>GNU/Linux Gentoo 
+</entry>
+<entry>AMD64, PowerPC, SPARC, x86 
+</entry>
+</row>
+<row>
+<entry>GNU/Linux Gentoo 
+</entry>
+<entry>AMD64, PowerPC, SPARC, x86 
+</entry>
+</row>
+<row>
+<entry>GNU/Linux Maemo 2.1 
+</entry>
+<entry>ARMv5t</entry>
+</row>
+<row>
+<entry>GNU/Linux Mandriva 2007 
+</entry>
+<entry></entry>
+</row>
+<row>
+<entry>GNU/Linux Open Zaurus 
+</entry>
+<entry>ARM 
+</entry>
+</row>
+<row>
+<entry>GNU/Linux OpenSuSE 10 
+</entry>
+<entry>i586, x86-64 
+</entry>
+</row>
+<row>
+<entry>GNU/Linux Red Hat 
+</entry>
+<entry>x86-32, x86-64 
+</entry>
+</row>
+<row>
+<entry>GNU/Linux Ubuntu 
+</entry>
+<entry>x86-64 reported working, also x86-32 and UltraSPARC 
+</entry>
+</row>
+<row>
+<entry>Haiku</entry>
+<entry></entry>
+</row>
+<row>
+<entry>Irix 6.5 
+</entry>
+<entry>MIPS R10K 
+</entry>
+</row>
+<row>
+<entry>MacOS X 
+</entry>
+<entry>PowerPC and x86-32 
+</entry>
+</row>
+<row>
+<entry>NetBSD</entry>
+<entry>many, including VAX
+</entry>
+</row>
+<row>
+<entry>OpenBSD</entry>
+<entry>many, including VAX, OS/2 and eComstation</entry>
+</row>
+<row>
+<entry>Windows</entry>
+<entry>x86-32</entry>
+</row>
+</tbody>
+</tgroup>
+</table>
+
+</sect2>
+
+<sect2 id="software">
+<title>Software Requirements</title>
+
+<para>
+The &appversion; release of &app; has been designed to run on UNIX/Linux 
variants, and has been run on most of the free ones.  However, &app; has 
successfully run on Windows, Darwin (Mac OS X), Irix, Solaris, BeOs, OS/2, and 
Haiku.  &app; has also run on the following 64-bit systems: PowerPC, Itanium, 
UltraSparc, and AMD64.   For now, it is important to be sure that the following 
code, testing, and documentation dependencies are met before installing &app;.  
If you will be downloading &app; with a package manager, these dependencies may 
be solved by the package manager.  Otherwise, you must first verify that each 
of these dependencies are installed on the target system.
+</para>
+
+ <sect3 id="codedepend">
+       &codedependencies;
+    </sect3>
+
+ <sect3 id="testdepend">
+       &testdependencies;
+    </sect3>
+
+<sect3 id="docdepend">
+       &docdependencies;
+    </sect3>
 </sect2>
 
 </sect1>
@@ -66,7 +200,7 @@
 <title>Downloading &app;</title>
 
 <para>
-There are two ways to download &app;: using a package manager or by 
downloading the source code and building it on your system.  If a package 
exists for your operating system and you do not need the very latest version of 
&app;, it is advisable to use a package manager, which can resolve 
dependencies.  However, if you want the very latest features, or a &app; 
package is not available for your operating system, it is better to download 
the source code and build &app; locally.
+There are two ways to download &app;: using a package manager or by 
downloading the source code and building it on your system. If possible, it is 
advisable to use a package manager to download &app;, as it will resolve 
dependencies for you.  However, if you want the very latest features, or a 
&app; package is not available for your operating system, it is better to 
download the source code and build &app; locally.
 </para>
 
   <sect2 id="packagemanager">
@@ -108,23 +242,26 @@
 
     <para>
       The latest development sources are available via
-      anonymous CVS (leave the password blank).  This is recommended
+      anonymous CVS.  This is recommended
       if you need features or bug fixes which were introduced after
       the <link linkend="sourcereleases">last release</link>.  Look at
       the <link linkend="sourcesnapshot">daily snapshot</link> if you
       experience difficulty accessing the repository.
     </para>
     <para>
-      First set the
-      environment variable <emphasis>CVS_RSH</emphasis> to 'ssh', as shown
-      in this example, which uses the GNU Bourne-Again shell (bash):
-      <programlisting>
-  export CVS_RSH="ssh"
-  cvs -z3 -d:pserver:address@hidden:/sources/gnash co gnash
-      </programlisting>
-      It is also possible to
+To download via anonymous CVS, first set the
+      environment variable <command>CVS_RSH</command> to 
<command>ssh</command>, then check out the source code.  The example below uses 
the GNU Bourne-Again shell (bash):
+</para>
+
+<screen>
+export CVS_RSH="ssh"
+cvs -z3 -d:pserver:address@hidden:/sources/gnash co gnash
+</screen>
+
+<para>
+      It is also possible to browse the repository
       <ulink url="http://cvs.savannah.gnu.org/viewcvs/gnash/?root=gnash";
-      type="http">browse the repository</ulink> on the web.
+      type="http" /> on the web.
     </para>
   </sect3>
 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]