Add GNOME 2.16 upgrade instructions.

This commit is contained in:
Joe Marcus Clarke 2006-10-14 16:45:32 +00:00
parent edff5224be
commit cc5a7aabdc
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/www/; revision=28857
2 changed files with 127 additions and 1 deletions

View file

@ -1,4 +1,4 @@
# $FreeBSD: www/en/gnome/docs/Makefile,v 1.20 2006/04/30 05:20:38 marcus Exp $
# $FreeBSD: www/en/gnome/docs/Makefile,v 1.21 2006/08/19 21:20:35 hrs Exp $
.if exists(../Makefile.conf)
.include "../Makefile.conf"
@ -12,6 +12,7 @@ DOCS+= faq28.sgml
DOCS+= faq210.sgml
DOCS+= faq212.sgml
DOCS+= faq214.sgml
DOCS+= faq216.sgml
DOCS+= gnome_porting.sgml
DOCS+= gnome1_porting.sgml
DOCS+= gnome2_porting.sgml

125
en/gnome/docs/faq216.sgml Normal file
View file

@ -0,0 +1,125 @@
<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [
<!ENTITY base CDATA "../../">
<!ENTITY date "$FreeBSD: www/en/gnome/docs/faq214.sgml,v 1.10 2006/08/19 21:20:35 hrs Exp $">
<!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.16/notes/en/">http://www.gnome.org/start/2.14/notes/en/</a>,
some of the most exciting new features of GNOME &gnomever; are:</p>
<ul>
<li>HAL support for FreeBSD!</li>
<li>MUCH better performance in large applications like
Evolution</li>
<li>Better power management and media/volume integration</li>
<li>Solid menu editing support</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 much simpler than it has been in the past:</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 -rf glib-2\* cairo gnome-doc-utils gnome-mime-data \
gnome-audio startup-notification dbus
</pre>
<p>Then you can run <tt>portupgrade(8)</tt> as you normally
would. <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</tt> user, the following will
work:
<pre>
# portmaster -r pkg-config\*
</pre>
<p>Then run portmaster normally.</p>
</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>
<p>There are currently no known issues with GNOME
&gnomever;.</p>
</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>