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

Clean up some grammar, add some tips, do some other stuff, and some other thing.

Browse source
This commit is contained in:
Adam Weinberger 2003-12-28 00:48:28 +00:00
parent 2e4ae912ed
commit 05e0ca35bf
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=19309
1 changed files with 24 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

35
en/gnome/docs/faq2.sgml
View file

@ -1,6 +1,6 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD: www/en/gnome/docs/faq2.sgml,v 1.54 2003/12/25 05:06:57 marcus Exp $">
<!ENTITY date "$FreeBSD: www/en/gnome/docs/faq2.sgml,v 1.55 2003/12/28 00:27:25 adamw Exp $">
<!ENTITY title "FreeBSD GNOME Project: GNOME &gnomever; FAQ">
<!ENTITY % gnomeincludes SYSTEM "../includes.sgml"> %gnomeincludes;
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
@ -176,6 +176,15 @@ options _KPOSIX_PRIORITY_SCHEDULING
If you do not need these ports installed, it is recommended that
you remove them.
</p>
<p>A common source of build failures is the existence of multiple versions
of the same library. This can happen if you have two different versions of
a port installed, or can even happen through normal <tt>portupgrade</tt> use.
You can back up the libraries in <tt>/usr/local/lib/compat/pkg</tt> and remove
them, and then run <tt>portupgrade -u -rf pkgconfig</tt>. This will force a
rebuild of all GNOME-related apps (and a fair number of other apps) without
retaining old versions of libraries in <tt>/usr/local/lib/compat/pkg</tt>.
</p>
</li>
<!-- Q3 -->
@ -214,13 +223,11 @@ options _KPOSIX_PRIORITY_SCHEDULING
<li style="padding-bottom: 0.5em"><a name="q4"></a>
<p><b>What is the best way to upgrade from GNOME 1.4 to GNOME 2?</b></p>
<!-- A4 -->
<p>Right now, the GNOME project is still very much in flux.
Work still must be done to the GNOME ports infrastructure in
order to get things working cleanly. However, if you have
<p>If you have
GNOME 1.4, and you want to upgrade to GNOME &gnomever;, first
familiarize yourself with the <a href="http://www.gnome.org/start/2.0/installation.html#upgrading">official</a> upgrade instructions from
the GNOME site. Next, make sure your GNOME 1.4 ports are
up-to-date, then remove the following GNOME 1.4 packages from
the GNOME site. Make sure your GNOME 1.4 ports are
up-to-date, and then remove the following GNOME 1.4 packages from
the system:</p>
<pre>
@ -242,8 +249,8 @@ eog
ggv
</pre>
<p>After those packages are removed, you can build GNOME &gnomever; per
the instructions listed above.</p>
<p>After those packages are removed, you can build GNOME &gnomever; as per
the <a href="#q1">instructions listed above</a>.</p>
</li>
@ -251,12 +258,13 @@ ggv
<li style="padding-bottom: 0.5em"><a name="q5"></a>
<p><b>What is the best way to upgrade from GNOME 2.2 to GNOME &gnomever;?</b></p>
<!-- A5 -->
<p>We recommend to use <tt>/usr/ports/sysutils/portupgrade</tt>
for such purpose. This will do the job well:</p>
<p>We recommend that you use <tt>/usr/ports/sysutils/portupgrade</tt>
for this purpose. The following will do the job well:</p>
<pre>
# pkgdb -F
(answer yes to all prompts)
(answer yes to all prompts; note that you might wish
to run the above command after each step below)
# portupgrade ORBit2 libbonobo
# portupgrade -rf -m BATCH=yes atk
# portupgrade -R -m BATCH=yes gnome2
@ -361,6 +369,11 @@ gnome-session-save --gui
window manager will revert back to the one previously configured
upon next login. To switch back, simply reverse sawfish and
metacity.</p>
<p>If you have gotten the GNOME &gnomever; desktop working under an
alternative window manager, please take a screenshot and
<a href="mailto:&email;@FreeBSD.org">send it to us</a>!
</p>
</li>
<!-- Q10 -->