diff --git a/en/gnome/docs/Makefile b/en/gnome/docs/Makefile index 97eccae2a7..296377bec9 100644 --- a/en/gnome/docs/Makefile +++ b/en/gnome/docs/Makefile @@ -1,31 +1,32 @@ -# $FreeBSD: www/en/gnome/docs/Makefile,v 1.27 2009/01/11 22:11:15 marcus Exp $ +# $FreeBSD: www/en/gnome/docs/Makefile,v 1.28 2009/04/11 03:10:05 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+= faq228.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/faq228.sgml b/en/gnome/docs/faq228.sgml new file mode 100644 index 0000000000..a7975218e8 --- /dev/null +++ b/en/gnome/docs/faq228.sgml @@ -0,0 +1,145 @@ + + + + +]> + + &header; + +

Contents

+
    +
  1. What is new in GNOME &gnomever;? +
  2. How do I upgrade to GNOME &gnomever;? +
  3. The upgrade failed; what do I do? +
  4. List of known GNOME &gnomever; problems and their solutions +
  5. I have found a bug; whom should I alert? +
  6. I want the fame and glory of the FreeBSD GNOME team! What + can I do to participate? +
+ +

Full Text

+
    + +
  1. +

    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;/, + some of the most exciting new features of GNOME &gnomever; are:

    + + + +
    2. + + +
  2. +

    How do I upgrade to GNOME &gnomever;?

    + +

    The answer is relatively simple:

    + +
      +
    1. +

      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. Then do the following:

      + 
      +# pkgdb -Ff
+(resolve all moved or deleted ports)
+
+# portupgrade -aW
+
      + +

      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 1.9 version. Then do the following:

      + + 
      +# portmaster -a
+
      + +
    +
    3. + + +
  3. +

    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.

    +
    4. + + +
  4. +

    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:

    + + +
    5. + + +
  5. +

    I have found a bug; whom should I alert?

    + +

    Please read the FreeBSD GNOME Project's + documentation on reporting bugs. +

    +
    6. + + +
  6. +

    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! +

    +
    7. +
+ + &footer; + +