diff --git a/en/gnome/docs/Makefile b/en/gnome/docs/Makefile index eb2ee8774a..b236dc2fb4 100644 --- a/en/gnome/docs/Makefile +++ b/en/gnome/docs/Makefile @@ -1,33 +1,34 @@ -# $FreeBSD: www/en/gnome/docs/Makefile,v 1.29 2009/11/29 20:28:43 marcus Exp $ +# $FreeBSD: www/en/gnome/docs/Makefile,v 1.30 2010/05/10 19:33:23 kwm 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+= faq228.sgml DOCS+= faq230.sgml +DOCS+= faq232.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/faq232.sgml b/en/gnome/docs/faq232.sgml new file mode 100644 index 0000000000..6f8c1dfc3b --- /dev/null +++ b/en/gnome/docs/faq232.sgml @@ -0,0 +1,124 @@ + + + + +]> + + &header; + +
What is new in GNOME &gnomever;?
+ +Although the canonical summary of new features can be found at + + http://library.gnome.org/misc/release-notes/&gnomever;/
+ +How do I upgrade to GNOME &gnomever;?
+ +The answer is relatively simple:
+ +To build GNOME &gnomever;, 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.
+ If you are a portupgrade(1) users, Then do the following: ++# pkgdb -fF +# pkg_deinstall -f0 gtkmm-2.20\* gtk-2.20\* +# portupgrade -aOW ++ +
NOTE: it is recommended to run portupgrade + -a to make sure you get all the necessary ports. The + -W option simply makes things a bit faster by not doing a + make clean after each port build.
+ +If you are a portmaster(8) user, make sure you have + least 3.1 version. Then do the following:
+ ++# pkg_delete -f gtkmm-2.20\* gtk-2.20\* +# portmaster -a ++ +
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 &gnomever; problems and their solutions
+ +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:
+ +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! +
+