diff --git a/en/gnome/docs/faq226.html b/en/gnome/docs/faq226.html deleted file mode 100644 index 58449e89dc..0000000000 --- a/en/gnome/docs/faq226.html +++ /dev/null @@ -1,281 +0,0 @@ - - - - -FreeBSD GNOME Project: GNOME 2.24 Upgrading FAQ - - - - - - - - - -
-
Skip site navigation (1) Skip section -navigation (2) - -
- - -

Site Navigation

- - -
- -
- - -
-

FreeBSD GNOME Project: GNOME 2.24 Upgrading FAQ

- -

Contents

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

Full Text

- -
    -
  1. - -

    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:

    - -
      -
    • A FreeBSD port of libxul-1.9 has been added as an alternative Gecko provider to -Firefox 2. This can be used by setting WITH_GECKO=libxul in -/etc/make.conf.
      • - -
    • The Brasero disc burning application has been added to the Desktop to replace -nautilus-cd-burner.
      • - -
    • The pulseaudio sound system has been made part of the Desktop to replace ESounD. This -provides more comprehensive sound support.
      • - -
    • Personal file sharing (WebDAV) has been added.
      • -
    -
    2. - -
  2. - -

    How do I upgrade to GNOME 2.24?

    - -

    The answer is relatively simple:

    - -
      -
    1. -

      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
-     
-
      -
      2. -
    -
    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 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:

    - -
      -
    • HAL can not unmount and reset the da[0-9] devices associated with USB disks -when you manually detach them from the system. Manually removing a USB umass device while -it is mounted can result in a panic. This is a known bug in FreeBSD. See kern/103258 and kern/89102 for more -details.
      • -
    -
    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. -
-
- -
-
- - -
-
- - - diff --git a/en/gnome/docs/faq226.sgml b/en/gnome/docs/faq226.sgml new file mode 100644 index 0000000000..3d0fbae5b4 --- /dev/null +++ b/en/gnome/docs/faq226.sgml @@ -0,0 +1,135 @@ + + + + +]> + + &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
+(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
+
      + +
    +
    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; + +