From d3b8d8cde2298950c4a9e1163064af3e7c339a98 Mon Sep 17 00:00:00 2001 From: Joe Marcus Clarke Date: Sun, 18 Jan 2004 21:33:19 +0000 Subject: [PATCH] * Update the list of known issues, and add a new bug * Mention the gnome_upgrade.sh script as a way to upgrade from GNOME 2.4 to 2.5. --- en/gnome/docs/develfaq.sgml | 93 +++++++++++++++++++------------------ 1 file changed, 47 insertions(+), 46 deletions(-) diff --git a/en/gnome/docs/develfaq.sgml b/en/gnome/docs/develfaq.sgml index a202689419..12afd21d5f 100644 --- a/en/gnome/docs/develfaq.sgml +++ b/en/gnome/docs/develfaq.sgml @@ -1,6 +1,6 @@ - + %gnomeincludes; %includes; @@ -16,11 +16,11 @@
  • How do I keep everything up-to-date and in sync?
  • What should I do when something does not work?
  • How can I help with the development versions? -
  • What is the current state of development GNOME on +
  • What is the current state of development GNOME on FreeBSD -

    Full Text

    +

    Full Text

      @@ -31,22 +31,22 @@ project that will eventually become the stable (release) versions. There are three working branches of GNOME development:

        -
      1. STABLE - The applications and libraries in the stable - branch are considered "release quality," and are the versions that - appear in the FreeBSD ports tree. The current stable version is - GNOME &gnomever;.
        2. -
      2. DEVELOPMENT - In between stable releases are development - releases. Traditionally, GNOME development releases have odd minor - numbers (e.g. 2.3, &gnomedevelver;, 2.(n*2)-1). Development releases will +
      3. STABLE - The applications and libraries in the stable + branch are considered "release quality," and are the versions that + appear in the FreeBSD ports tree. The current stable version is + GNOME &gnomever;.
        4. +
      4. DEVELOPMENT - In between stable releases are development + releases. Traditionally, GNOME development releases have odd minor + numbers (e.g. 2.3, &gnomedevelver;, 2.(n*2)-1). Development releases will become stable releases, and move from alpha to beta quality during - their lifecycle. The development releases need testing by FreeBSD - users to minimize the number of surprises when the new stable - versions are committed to the FreeBSD CVS tree. This document is + their lifecycle. The development releases need testing by FreeBSD + users to minimize the number of surprises when the new stable + versions are committed to the FreeBSD CVS tree. This document is about the development branch. The current development branch - is GNOME &gnomedevelver;.
        5. + is GNOME &gnomedevelver;.
      5. CVS - Often newer-than-new, the CVS HEAD versions of GNOME applications and libraries are alpha quality, or often completely - unbuildable. The FreeBSD GNOME project pays attention to, but + unbuildable. The FreeBSD GNOME project pays attention to, but does not track the alpha quality code.
      @@ -56,9 +56,9 @@

      Should I track GNOME development versions?

      If you are looking for a stable environment, absolutely not. Please - only track the GNOME &gnomedevelver; branch if you wish to help identify bugs - and improve the FreeBSD GNOME project. You will find little - sympathy if a development-quality GNOME application eats your + only track the GNOME &gnomedevelver; branch if you wish to help identify bugs + and improve the FreeBSD GNOME project. You will find little + sympathy if a development-quality GNOME application eats your homework.

      @@ -66,12 +66,12 @@

    1. How do I obtain the development versions of GNOME stuff?

      -

      Marcus maintains a - CVS repository where all the development versions of +

      Marcus maintains a + CVS repository where all the development versions of the GNOME components for FreeBSD are housed. Instructions for - how to check out the development ports module and how to merge it - into the FreeBSD ports tree reside on the entrance page to his - repository. Please read carefully the instructions at + how to check out the development ports module and how to merge it + into the FreeBSD ports tree reside on the entrance page to his + repository. Please read carefully the instructions at http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi.

      @@ -88,17 +88,21 @@ STRIP=

    2. How do I keep everything up-to-date and in sync?

      -

      The short answer is that you need to use the marcusmerge +

      The short answer is that you need to use the marcusmerge script to merge the development tree with the FreeBSD ports tree. The marcusmerge script is available here, and a man page on useing the script is available here. This script will merge the development ports tree - into your main ports tree. From there, you can use - portupgrade to stay + into your main ports tree. From there, you can download + the + gnome_upgrade.sh script to aid in upgrading from GNOME + 2.4 to &gnomedevelver;. Once you are running GNOME + &gnomedevelver;, you can use portupgrade to stay up-to-date.

      - +

      The long answer is that keeping up-to-date with the GNOME development branch is complicated. Sometimes components change in a way that makes portupgrade fail, or causes strange end results. @@ -108,7 +112,7 @@ STRIP= freebsd-gnome mailing list, as well as to join the #freebsd-gnome IRC channel on FreeNode (irc.freenode.net).

      -

      If all of this sounds scary, or you need a desktop that +

      If all of this sounds scary, or you need a desktop that "Just Works," you should stick with the stable GNOME branch.

      3. @@ -120,13 +124,13 @@ STRIP= GNOME component, you can report a bug using bug-buddy or the GNOME BugZilla interface (NOTE: Evolution's BugZilla interface can be - found here). If you think - the problem lies in a FreeBSD port, or is FreeBSD-specific, send + found here). If you think + the problem lies in a FreeBSD port, or is FreeBSD-specific, send email to &email;@FreeBSD.org, or report the problem on the #freebsd-gnome IRC channel on FreeNode.

      -

      Please forward all GNOME/Ximian bug IDs to +

      Please forward all GNOME/Ximian bug IDs to &email;@FreeBSD.org so we can keep track of known issues. Thanks!

      @@ -139,7 +143,7 @@ STRIP= many good bugs as possible. We also need people with artistic skills to create some hot screenshots.

      - +

      If you like coding, and you know Perl, we really need someone to help in porting @@ -158,23 +162,17 @@ STRIP=

    3. What is the current state of development GNOME on FreeBSD?

      -

      Development versions of the entire GNOME &gnomedevelver; desktop environment are - available, and they all compile cleanly.

      +

      Development versions of the entire GNOME &gnomedevelver; desktop + environment are available, and they all compile cleanly.

      Most of the components of x11/gnome2-fifth-toe have working - development versions. None of the apps that use the C++ + development versions. None of the apps that use the C++ bindings work yet; the C++ bindings themselves are there, but none of the Fifth Toe apps will currently compile against them.

      - -

      After updating to libgnomeui-2.5.2, some ports may refuse to build - You may also notice some components are unable to load their - icons.

      - -

      Users may not be able to logout under GNOME 2.5.1. The symptom is - the desktop hangs after selecting Actions->Log Out. The - workaround is to disable "Prompt on logout" under - Applications->Desktop Preferences->Advanced->Sessions.

      - + +

      After updating to libgnomeui-2.5.2, some components (e.g. + gnome-panel) are unable to load their icons.

      +

      Desktop icons have read-only emblems. It is said this only happens for users in the wheel group.

      @@ -182,8 +180,11 @@ STRIP=
      • - #129349: [gnome-terminal] keybindings don't work if menu bar + #129349: [gnome-terminal] keybindings don't work if menu bar isn't visible
        • +
      • + #131828: [gnome-vfs] file type taking precedence over extension + type