Make a first pass at updating the documentation for GNOME 2.20.

This commit is contained in:
Joe Marcus Clarke 2007-10-25 16:56:37 +00:00
parent 3992dfef25
commit 82398795de
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/www/; revision=30941
4 changed files with 152 additions and 9 deletions

View file

@ -1,4 +1,4 @@
# $FreeBSD: www/en/gnome/docs/Makefile,v 1.22 2006/10/14 16:45:32 marcus Exp $
# $FreeBSD: www/en/gnome/docs/Makefile,v 1.23 2007/03/19 17:36:34 marcus Exp $
.if exists(../Makefile.conf)
.include "../Makefile.conf"
@ -14,6 +14,7 @@ DOCS+= faq212.sgml
DOCS+= faq214.sgml
DOCS+= faq216.sgml
DOCS+= faq218.sgml
DOCS+= faq220.sgml
DOCS+= gnome_porting.sgml
DOCS+= gnome1_porting.sgml
DOCS+= gnome2_porting.sgml

View file

@ -1,6 +1,6 @@
<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD: www/en/gnome/docs/faq2.sgml,v 1.126 2007/06/23 21:45:39 marcus Exp $">
<!ENTITY date "$FreeBSD: www/en/gnome/docs/faq2.sgml,v 1.127 2007/09/20 16:20:53 marcus Exp $">
<!ENTITY title "FreeBSD GNOME Project: GNOME &gnomever; FAQ">
<!ENTITY email "freebsd-gnome">
<!ENTITY % navinclude.gnome "INCLUDE">
@ -246,7 +246,7 @@ options _KPOSIX_PRIORITY_SCHEDULING
<p>Starting with 2.16, GNOME now lives in
<tt>LOCALBASE</tt> instead of <tt>X11BASE</tt>.
This move can cause strange build problems if <a
href="&base;/gnome/docs/faq218.html">the proper
href="&base;/gnome/docs/faq220.html">the proper
upgrade steps</a> are not followed. However, if
after following all the steps, you may still see
errors like the following:</p>
@ -368,7 +368,7 @@ libtool: link: `/usr/X11R6/lib/libglade-2.0.la' is not a valid libtool archive
<!-- A5 -->
<p>The &gnomeoldver; to &gnomever; may have a few
caveats. You are strongly advised to read the
<a href="faq218.html">upgrade FAQ</a> for detailed
<a href="faq220.html">upgrade FAQ</a> for detailed
instructions.</p>
</li>

142
en/gnome/docs/faq220.sgml Normal file
View file

@ -0,0 +1,142 @@
<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [
<!ENTITY base CDATA "../../">
<!ENTITY date "$FreeBSD$">
<!ENTITY title "FreeBSD GNOME Project: GNOME &gnomever; Upgrading FAQ">
<!ENTITY % navinclude.gnome "INCLUDE">
]>
<html>
&header;
<h2>Contents</h2>
<ol>
<li> <a href="#q1">What is new in GNOME &gnomever;?</a>
<li> <a href="#q2">How do I upgrade to GNOME &gnomever;?</a>
<li> <a href="#q3">The upgrade failed; what do I do?</a>
<li> <a href="#q4">List of known GNOME &gnomever; problems and their solutions</a>
<li> <a href="#q5">I have found a bug; whom should I alert?</a>
<li> <a href="#q6">I want the fame and glory of the FreeBSD GNOME team! What
can I do to participate?</a>
</ol>
<h2>Full Text</h2>
<ol>
<!-- Q1 -->
<li style="padding-bottom: 0.5em"><a name="q1"></a>
<p><b>What is new in GNOME &gnomever;?</b></p>
<!-- A1 -->
<p>Although the canonical summary of new features can be found at
<a
href="http://www.gnome.org/start/2.20/notes/en/">http://www.gnome.org/start/2.20/notes/en/</a>,
some of the most exciting new features of GNOME &gnomever; are:</p>
<ul>
<li>Seahorse has been added to integrate OpenPGP with the
Desktop.</li>
<li>Improved system monitoring with a cleaned up FreeBSD
backend for libgtop.</li>
<li>Two new games: gnome-sudoku and glChess.</li>
<li>Network support for many GNOME games.</li>
<li>Lots of stability and performance improvements.</li>
</ul>
</li>
<!-- Q2 -->
<li style="padding-bottom: 0.5em"><a name="q2"></a>
<p><b>How do I upgrade to GNOME &gnomever;?</b></p>
<!-- A2 -->
<p>The answer is relatively simple:</p>
<ol>
<li>
<p>To build GNOME &gnomever;, you need to obtain the latest
ports tree skeleton. This is most easily accomplished with
<tt>portsnap(8)</tt> or <a
href="http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html">CVSup</a>. Simply obtain the latest ports tree, and you are
ready to go. Then do the following:</p>
<pre>
# pkgdb -Ff
# portupgrade -f -o textproc/rarian textproc/scrollkeeper
# portupgrade -a
# pkgdb -fF
</pre>
<b>NOTE:</b> it is recommended to run <b>portupgrade
-a</b> to make sure you get all the necessary ports.</p>
<p>If you are a <tt>portmaster(8)</tt> user, make sure you have
least 1.9 version. Then do the following:</p>
<pre>
# portmaster -o textproc/rarian textproc/scrollkeeper
# portmaster -a
</pre>
</ol>
</li>
<!-- Q3 -->
<li style="padding-bottom: 0.5em"><a name="q3"></a>
<p><b>The upgrade failed; what do I do?</b></p>
<!-- A3 -->
<p>Unfortunately, this is not only possible, it is highly probable. There are many possible
valid GNOME configurations, and even more invalid starting points. If the script fails,
follow the instructions in the error message to let the FreeBSD GNOME team know about the
failure.</p>
<p>The majority of build failures will be dependency-related issues. One simple way to resolve
the problem is to remove the offending port, re-run <tt>portupgrade</tt> or <tt>portmaster</tt>, and then
reinstall the port when the upgrade process is complete.</p>
</li>
<!-- Q4 -->
<li style="padding-bottom: 0.5em"><a name="q4"></a>
<p><b>List of GNOME &gnomever; problems and their solutions</b></p>
<!-- A4 -->
<p>Although GNOME &gnomever; is certainly the best release to date (of course), there are
a couple regressions that slipped in, both in the GNOME code and in its implementation
within FreeBSD. Some of the more visible issues are:</p>
<ul>
<li><tt>hald-addon-storage</tt> consumes file descriptors
until it crashes. This is a known bug in FreeBSD, and only
affects 6.0 and earlier and 5.5 and earlier. Users on those
releases are encouraged to upgrade to FreeBSD 6.1 or
later.</li>
<li><b>HAL</b> can not unmount and reset the da[0-9] devices
associated with USB disks when you manually detach them from
the system. Manually removing a USB umass device while it
is mounted can result in a panic. This is a known bug in FreeBSD.
See <a href="http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/103258">kern/103258</a> and <a href="http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/89102">kern/89102</a> for more details.</li>
<li>Some users have reported problems with Yelp displaying an
error trying to view help files on FreeBSD 6.X. The problem
does not appear to exist on 7.X or 8.X, nor is it reliably
reproducible. If you are encountering this problem, please
notify <a
href="mailto:&email;@FreeBSD.org">&email;@FreeBSD.org</a>.
</ul>
</li>
<!-- Q5 -->
<li style="padding-bottom: 0.5em"><a name="q5"></a>
<p><b>I have found a bug; whom should I alert?</b></p>
<!-- A5 -->
<p>Please read the FreeBSD GNOME Project's
<a href="http://www.FreeBSD.org/gnome/docs/bugging.html">documentation on reporting bugs</a>.
</p>
</li>
<!-- Q6 -->
<li style="padding-bottom: 0.5em"><a name="q6"></a>
<p><b>I want the fame and glory of being part of the FreeBSD GNOME team!
What can I do to participate?</b></p>
<!-- A6 -->
<p>Please read our list of <a href="http://www.FreeBSD.org/gnome/docs/volunteer.html">ways
to get involved</a>!
</p>
</li>
</ol>
&footer;
</body>
</html>

View file

@ -4,7 +4,7 @@
<!ENTITY title "The FreeBSD GNOME Project">
<!ENTITY % navinclude.gnome "INCLUDE">
]>
<!-- $FreeBSD: www/en/gnome/index.xsl,v 1.94 2007/04/16 05:19:08 marcus Exp $ -->
<!-- $FreeBSD: www/en/gnome/index.xsl,v 1.95 2007/07/10 20:26:23 ahze Exp $ -->
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
@ -122,16 +122,16 @@
developers and users that manage the
integration of GNOME and FreeBSD.</p>
<h2>Upgrading to GNOME 2.18?</h2>
<h2>Upgrading to GNOME 2.20?</h2>
<p>If you are upgrading from GNOME 2.16 to GNOME 2.18, read the
<a href="docs/faq218.html">Upgrade FAQ</a> for upgrade
<p>If you are upgrading from GNOME 2.18 to GNOME 2.20, read the
<a href="docs/faq220.html">Upgrade FAQ</a> for upgrade
instructions.</p>
<h2>State of the port</h2>
<p>GNOME for FreeBSD is currently supported on
5-STABLE, 6-STABLE, 7-CURRENT, 5.5, 6.1, and 6.2.
5-STABLE, 6-STABLE, 7.X, 8-CURRENT, 5.5, 6.1, and 6.2.
Most of GNOME has been ported to FreeBSD, but there is still
<a href="docs/volunteer.html">plenty left to be done</a>!</p>