From 6f1c89530bfa2551af25cab092065ec058a012b4 Mon Sep 17 00:00:00 2001
From: Jeremy Messenger
-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
The long answer is that keeping up-to-date with the GNOME development branch is complicated. Sometimes components change - in a way that makes portupgrade 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 portupgrade or portmaster + fail, or causes strange end results. If you plan to track the + development branch, it is a good idea to join the freebsd-gnome mailing list, as well as to join the - #freebsd-gnome IRC channel on FreeNode (irc.freenode.net).
+ #freebsd-gnome IRC channel on FreeNode + (irc.freenode.net).If all of this sounds scary, or you need a desktop that "Just Works," you should stick with the stable GNOME branch.
@@ -164,7 +171,7 @@ portupgrade -rf glib-2\* cairo gnome-doc-utils gnome-mime-data gnome-audioWhat is the current state of development GNOME on FreeBSD?
-GNOME 2.19.6 is now out, and ports and packages are +
GNOME 2.20.0 is now out, and ports and packages are up-to-date. Keep those bug reports coming.