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

Update a guide of how to upgrade from 2.18 to 2.20. Add portmaster in it.

Browse source
This commit is contained in:
Jeremy Messenger 2007-09-27 05:09:08 +00:00
parent c92e118cfc
commit 6f1c89530b
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=30829
1 changed files with 19 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

31
en/gnome/docs/develfaq.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/develfaq.sgml,v 1.51 2007/06/21 06:55:20 marcus Exp $">
<!ENTITY date "$FreeBSD: www/en/gnome/docs/develfaq.sgml,v 1.52 2007/09/11 01:20:16 bland Exp $">
<!ENTITY title "FreeBSD GNOME Project: GNOME Development Branch FAQ">
<!ENTITY email "freebsd-gnome">
<!ENTITY % navinclude.gnome "INCLUDE">
@ -108,24 +108,31 @@ WITH_DEBUG=yes
<a href="http://www.marcuscom.com/marcusmerge.8.html">
here</a>. This script will merge the development ports tree
into your main ports tree. From there, you can use
<tt>portupgrade</tt> to upgrade from &gnomever; to &gnomedevelver;
and stay up-to-date afterwards. <b>NOTE:</b> if this is a
first-time upgrade from &gnomever; to &gnomedevelver; you
must run a special <tt>portupgrade</tt> command to account
for the move from <tt>X11BASE</tt> to <tt>LOCALBASE</tt>:</p>
<tt>portupgrade</tt> or <tt>portmaster</tt> to upgrade from
&gnomever; to &gnomedevelver; and stay up-to-date afterwards.
<b>NOTE:</b> if this is a first-time upgrade from &gnomever; to
&gnomedevelver; you must run <tt>portupgrade</tt> or
<tt>portmaster</tt> command:</p>
<pre>
portupgrade -rf glib-2\* cairo gnome-doc-utils gnome-mime-data gnome-audio
portupgrade -o textproc/rarian textproc/scrollkeeper
portupgrade -a
or
portmaster -o textproc/rarian textproc/scrollkeeper
portmaster -a
</pre>
<p>The long answer is that keeping up-to-date with the GNOME
development branch is complicated. Sometimes components change
in a way that makes <tt>portupgrade</tt> fail, or causes strange end results.
If you plan to track the development branch, it is a good idea
to join the
in a way that makes <tt>portupgrade</tt> or <tt>portmaster</tt>
fail, or causes strange end results. If you plan to track the
development branch, it is a good idea to join the
<a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-gnome">
freebsd-gnome</a> mailing list, as well as to join the
<em>#freebsd-gnome</em> IRC channel on FreeNode (<tt>irc.freenode.net</tt>).</p>
<em>#freebsd-gnome</em> IRC channel on FreeNode
(<tt>irc.freenode.net</tt>).</p>
<p>If all of this sounds scary, or you need a desktop that
"Just Works," you should stick with the stable GNOME branch.</p>
@ -164,7 +171,7 @@ portupgrade -rf glib-2\* cairo gnome-doc-utils gnome-mime-data gnome-audio
<li style="padding-bottom: 0.5em"><a name="q7"></a>
<p><b>What is the current state of development GNOME on FreeBSD?</b></p>
<!-- A7 -->
<p>GNOME 2.19.6 is now out, and ports and packages are
<p>GNOME 2.20.0 is now out, and ports and packages are
up-to-date. Keep those bug reports coming.</p>
</li>
</ol>