diff --git a/en/gnome/docs/Makefile b/en/gnome/docs/Makefile index 809afb07e2..97eccae2a7 100644 --- a/en/gnome/docs/Makefile +++ b/en/gnome/docs/Makefile @@ -1,30 +1,31 @@ -# $FreeBSD: www/en/gnome/docs/Makefile,v 1.26 2008/03/30 18:35:28 marcus Exp $ +# $FreeBSD: www/en/gnome/docs/Makefile,v 1.27 2009/01/11 22:11:15 marcus Exp $ .if exists(../Makefile.conf) .include "../Makefile.conf" .endif .if exists(../Makefile.inc) .include "../Makefile.inc" .endif DOCS= faq2.sgml DOCS+= faq28.sgml DOCS+= faq210.sgml DOCS+= faq212.sgml DOCS+= faq214.sgml DOCS+= faq216.sgml DOCS+= faq218.sgml DOCS+= faq220.sgml DOCS+= faq222.sgml DOCS+= faq224.sgml +DOCS+= faq226.sgml DOCS+= gnome_porting.sgml DOCS+= gnome1_porting.sgml DOCS+= gnome2_porting.sgml DOCS+= porting.sgml DOCS+= bugging.sgml DOCS+= volunteer.sgml DOCS+= develfaq.sgml DOCS+= example-Makefile.sgml DOCS+= halfaq.sgml .include "${WEB_PREFIX}/share/mk/web.site.mk" diff --git a/en/gnome/docs/faq226.html b/en/gnome/docs/faq226.html new file mode 100644 index 0000000000..bde2cfb90e --- /dev/null +++ b/en/gnome/docs/faq226.html @@ -0,0 +1,281 @@ + + +
+ +What is new in GNOME 2.24?
+ +Although the canonical summary of new features can be found at http://library.gnome.org/misc/release-notes/2.24/, +some of the most exciting new features of GNOME 2.24 are:
+ +How do I upgrade to GNOME 2.24?
+ +The answer is relatively simple:
+ +To build GNOME 2.24, you need to obtain the latest ports tree skeleton. This is most +easily accomplished with portsnap(8) or CVSup. +Simply obtain the latest ports tree, and you are ready to go. Then do the following:
+ ++# pkgdb -Ff +(Remove gnome-volume-manager.) + +# portupgrade -aOW +# portupgrade -f gnome-media gnome-settings-daemon gnome-control-center + ++ +
NOTE: it is recommended to run portupgrade -a to make sure you get all +the necessary ports.
+ +If you are a portmaster(8) user, make sure you have least 1.9 version. Then +do the following:
+ ++# portmaster -a +# portmaster gnome-media gnome-settings-daemon gnome-control-center + ++
The upgrade failed; what do I do?
+ +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.
+ +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 portupgrade or +portmaster, and then reinstall the port when the upgrade process is +complete.
+List of GNOME 2.24 problems and their solutions
+ +Although GNOME 2.24 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:
+ +I have found a bug; whom should I alert?
+ +Please read the FreeBSD GNOME Project's documentation on reporting +bugs.
+I want the fame and glory of being part of the FreeBSD GNOME team! What can I do to +participate?
+ +Please read our list of ways to get involved!
+
GNOME is a complete graphical desktop for X, including everything from a window manager to web browsers, audio players, office programs, and more.
The FreeBSD GNOME Project is a team of devoted developers and users that manage the integration of GNOME and FreeBSD.
The easiest way to install GNOME is to install either of the following ports:
And, as desired, one or all of:
If you are upgrading from GNOME 2.22 to GNOME 2.24, read the - Upgrade FAQ for upgrade +
If you are upgrading from GNOME 2.22 to GNOME 2.26, read the + Upgrade FAQ for upgrade instructions.
GNOME for FreeBSD is currently supported on - 6.4, 6-STABLE, 7.0, 7.1, 7-STABLE, and 8-CURRENT. + 6.4, 6-STABLE, 7.1, 7-STABLE, and 8-CURRENT. Most of GNOME has been ported to FreeBSD, but there is still plenty left to be done!
GNOME is simple and easy to build using the FreeBSD ports system, but sometimes things simply go wrong. If GNOME -- or anything that uses GNOME libraries -- is not building the way it should, simply run the gnomelogalyzer.sh tool from the directory of the failed port, and let the gnomelogalyzer figure out what's wrong and how to fix it!