os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Add the GNOME 2.28 upgrade page.

Browse source
This commit is contained in:
Joe Marcus Clarke 2009-11-29 20:28:43 +00:00
parent 78f46ec499
commit a0f0bf38fe
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=34996
2 changed files with 147 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

3
en/gnome/docs/Makefile
View file

@ -1,4 +1,4 @@
# $FreeBSD: www/en/gnome/docs/Makefile,v 1.27 2009/01/11 22:11:15 marcus Exp $
# $FreeBSD: www/en/gnome/docs/Makefile,v 1.28 2009/04/11 03:10:05 marcus Exp $
.if exists(../Makefile.conf)
.include "../Makefile.conf"
@ -18,6 +18,7 @@ DOCS+= faq220.sgml
DOCS+= faq222.sgml
DOCS+= faq224.sgml
DOCS+= faq226.sgml
DOCS+= faq228.sgml
DOCS+= gnome_porting.sgml
DOCS+= gnome1_porting.sgml
DOCS+= gnome2_porting.sgml

145
en/gnome/docs/faq228.sgml Normal file
View file

@ -0,0 +1,145 @@
<!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://library.gnome.org/misc/release-notes/&gnomever;/">http://library.gnome.org/misc/release-notes/&gnomever;/</a>,
some of the most exciting new features of GNOME &gnomever; are:</p>
<ul>
<li>Evolution MAPI support has been added to the FreeBSD port
to provide a richer experience for users of Microsoft Exchange
servers.</li>
<li>Epiphany now uses WebKit as its HTML/JavaScript rendering
engine.</li>
<li>Hal has been updated to fix some issues with volume
probing, and to support volume names (labels) that contain
spaces.</li>
<li>A preview of the GNOME Shell environment has been added to
the ports tree (<tt>x11/gnome-shell</tt>). This environment
is being slated to make its official appearance in GNOME 3.0.</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
(resolve all moved or deleted ports)
# portupgrade -aW
</pre>
<p><b>NOTE:</b> it is recommended to run <b>portupgrade
-a</b> to make sure you get all the necessary ports. The
-W option simply makes things a bit faster by not doing a
<tt>make clean</tt> after each port build.</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 -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><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>Epiphany no longer saves passwords. This should be fixed
in an upcoming release, but may get postponed until GNOME
2.30.</li>
<li>Epiphany has problems rendering certain compressed web
sites (most notably <a
href="http://www.freebsd.org/cgi/cvsweb.cgi/">http://www.freebsd.org/cgi/cvsweb.cgi/</a>).
The page will appear as compressed binary garbage. This is
being wored on, and should be fixed in an upcoming release of
libsoup.</li>
</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>