From 993c2fb8f0ccf3d80328712ccb9b7b27fef4df52 Mon Sep 17 00:00:00 2001 From: Jeremy Messenger Date: Sat, 5 Nov 2005 07:13:30 +0000 Subject: [PATCH] Copy from faq210.sgml with a small change, this is for GNOME 2.12. Changes: -Update GNOME's release note link to 2.12 -gnome_upgrade.sh (freebsd.org) -> gnome_upgrade212.sh (MC), I am not sure on this one. Please correct it if it is not correct. -Remove a entry from known issue, about gnome-menus's LegacyDir bug. --- en/gnome/docs/faq212.sgml | 206 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 206 insertions(+) create mode 100644 en/gnome/docs/faq212.sgml diff --git a/en/gnome/docs/faq212.sgml b/en/gnome/docs/faq212.sgml new file mode 100644 index 0000000000..ebc77d852e --- /dev/null +++ b/en/gnome/docs/faq212.sgml @@ -0,0 +1,206 @@ + + + + %navincludes; + %gnomeincludes; + %includes; +]> + + &header; + +

Contents

+
    +
  1. What is new in GNOME &gnomever;? +
  2. How do I upgrade to GNOME &gnomever;? +
  3. Oops! I ran portupgrade(1)! What do I do? +
  4. The upgrade failed; what do I do? +
  5. List of known GNOME &gnomever; problems and their solutions +
  6. I have found a bug; whom should I alert? +
  7. 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://www.gnome.org/start/2.12/notes/en/rnusers.html, + some of the most exciting new features of GNOME &gnomever; are:

    + +
      +
    • FreeBSD support for CPU frequency monitoring, ACPI power + management, wireless signal strength monitoring for all + supported drivers, and disk read/write utilization +
    • Better keyboard layout and feature control +
    • Sleek selection of desktop backgrounds +
    • Many new applications, applets, and UI enhancements +
    • Extensive list of stability and speed increases +
    + +
    2. + + +
  2. +

    How do I upgrade to GNOME &gnomever;?

    + +

    NOTE: Do not run portupgrade(1) to upgrade to GNOME &gnomever;!

    + +

    The simple answer is this:

    + +
      +
    1. CVSup + your ports tree. +
    2. Download the FreeBSD GNOME Project's upgrade + script. +
    3. Run the script as root. Read a good-sized book. +
    + +

    More detailed instructions are as follows:

    + +
      +
    1. CVSup your ports tree. + +

      To build GNOME &gnomever;, you need to obtain the &gnomever; ports tree skeleton. This is + most easily accomplished with CVSup. Simply obtain the latest ports tree, and you are + ready to go. After you have obtained the latest ports tree, do not run a typical + portupgrade(1).

      +
      2. + +
    2. Obtain the upgrade script. + +

      It is not possible to upgrade from GNOME &gnomeoldver; to GNOME &gnomever; by simply running + portupgrade(1). There are new dependencies, and ports will build out-of-order, + eventually causing the build to fail.

      + +

      To work around these problems, and to provide an update mechanism as simple as + portupgrade(1), the FreeBSD GNOME team has produced a comprehensive upgrade script. + The script can be downloaded from:

      + +
      http://www.FreeBSD.org/gnome/gnome_upgrade.sh +
      + +

      Simply download that script, and save it to disk.

      +
      3. + +
    3. Run the script. + +

      Once you have the script downloaded, run, as root:

      + + 
      +# sh ./gnome_upgrade.sh
+
      +

      Hit ENTER to begin, answer any questions that pop up, and go watch an + entire Monty Python anthology. Right after hitting ENTER at the beginning, + you will be given the path to a logfile. By running:

      + + 
      +$ tail -f /path/to/logfile
+
      +

      you can watch the entire upgrade process as it unfolds. It is hypnotic!

      +
      4. +
    +
    3. + + +
  3. +

    Oops! I ran portupgrade(1)! What do I do?

    + +

    Do not worry; hope is not lost. Running portupgrade(1) will cause the build + to fail, but it will not cause any lasting damage to your ports tree, unless you have + done something exceptionally creative. Simply download the gnome_upgrade.sh + script and run it, and pretend that you ran it in the first place. Nobody needs to know + that you did not read the directions first!

    +
    4. + + +
  4. +

    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 gnome_upgrade.sh, and then + reinstall the port when the upgrade process is complete. In + order to avoid having to build everything again, you can pass + the -restart flag to gnome_upgrade.sh to + resume a failed build.

    +
    5. + + +
  5. +

    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:

    + +
      +
    • Changing the GTK theme can cause a few apps to crash. This issue is known to the + GNOME/Linux world, so it is not a FreeBSD-specific issue. You can ignore + the error message, and click the "Restart" button to restart the + crashed application when the dialog pops up. You should be fine after that. +
    • The KDE menu is missing some icons. KDE failed to follow the published + freedesktop.org standards, and places its icons in a non-standard + location. GNOME 2.10 introduced a mass move towards complete compliance + with freedesktop.org standards, so there's not much that can be done + until KDE moves its default icons into a location that GNOME recognizes. + + http://standards.freedesktop.org/icon-theme-spec/icon-theme-spec-latest.html +
    • [gnome-session]: Options for shutting down or rebooting + will not appear on logout unless GDM is running on the + same machine. +
    • [multiload-applet]: The disk reads/writes monitor does + not work on -CURRENT. A solution is currently being + sought. +
    • + #137388: [gnome-terminal] gnome-terminal has a problem + with dynamic titles and vim (UPDATE: See this + email + for a workaround to this problem) +
    • #73375: + [evolution] Evolution will crash when selecting a new + Server Type for an account with malloc debugging enabled. + This only affects -CURRENT users by default. To disable + malloc debugging, run the command ln -sf aj + /etc/malloc.conf as root. +
    • GnomeVFS-2 now has native support for sftp methods. Fully + non-interactive publickey authentication works on all versions + of FreeBSD, but FreeBSD 5.X is required for password or + passphrase authentication. +
    + +
    6. + + +
  6. +

    I have found a bug; whom should I alert?

    + +

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

    +
    7. + + +
  7. +

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

    +
    8. +
+ + &footer; + +