diff --git a/en_US.ISO8859-1/htdocs/gnome/docs/develfaq.xml b/en_US.ISO8859-1/htdocs/gnome/docs/develfaq.xml index 39008a862c..f28316a36e 100644 --- a/en_US.ISO8859-1/htdocs/gnome/docs/develfaq.xml +++ b/en_US.ISO8859-1/htdocs/gnome/docs/develfaq.xml @@ -1,172 +1,174 @@ ]> &title; $FreeBSD$

Contents

  1. What are development versions of GNOME all about?
  2. Should I track development versions?
  3. How do I obtain development versions of GNOME stuff?
  4. How do I keep everything up-to-date and in sync?
  5. What should I do when something does not work?
  6. How can I help with the development versions?
  7. What is the current state of development GNOME on - FreeBSD
    8. + &os;

Full Text

  1. What are development versions of GNOME all about?

    The development versions are the packages released by the GNOME 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 + appear in the &os; ports tree. The current stable version is GNOME &gnomever;.
    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 + numbers (e.g. 2.3, &gnomedevelver;, 3.(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 + their lifecycle. The development releases need testing by &os; 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;.
      3. + versions are committed to the &os; SVN tree. This document is + about the development branch. At any time the development branch for &os; + might be based of a stable GNOME release. However it will be tagged + "development" here if it is the version that is work in progress by the &os; + GNOME team. The current development branch for &os; is GNOME &gnomedevelver;.
    3. GIT - Often newer-than-new, the GIT master versions of GNOME applications and libraries are alpha quality, or often completely - unbuildable. The FreeBSD GNOME project pays attention to, but + unbuildable. The &os; GNOME project pays attention to, but does not track the alpha quality code.

  2. 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 + and improve the &os; GNOME project. You will find little sympathy if a development-quality GNOME application eats your homework.

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

    Marcus maintains a - CVS repository where all the development versions of - the GNOME components for FreeBSD are housed. Instructions for + SVN repository where all the development versions of + the GNOME components for &os; 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 + into the &os; ports tree reside on the entrance page to his SVN repository. Please read carefully the instructions at - http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi. + http://www.marcuscom.com:8080/viewvc/viewvc.cgi/marcuscom/.

    During the development cycle, FreeBSD-specific caveats and other useful information will be sent to marcuscom-devel@marcuscom.com. If you are tracking the GNOME development branch, you must subscribe to this list. You should also consider subscribing to &email;@FreeBSD.org.

    In order to help with bug reports, be sure to add the following to /etc/make.conf so that gdb back traces contain useful information:

     WITH_DEBUG="yes"
    -

    GNOME has an excellent guide for getting +

    GNOME has an excellent guide for getting useful back traces.

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

    The short answer is that you need to use the marcusmerge - script to merge the development tree with the FreeBSD ports tree. + script to merge the development tree with the &os; ports tree. The marcusmerge script is available here, and a man page on using the script is available here. This script will merge the development ports tree into your main ports tree. From there, you can use portupgrade or portmaster to upgrade from &gnomever; to &gnomedevelver; and stay up-to-date afterwards.

    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 or portmaster fail, or causes strange end results. If you plan to track the development branch, it is a good idea to join the 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 - "Just Works," you should stick with the stable GNOME branch.

    + "Just Works," you should stick with the &gnomever; version that + is available in the &os; ports tree.

  5. What should I do when something does not work?

    It depends. If you think the problem is truly a bug with the GNOME component, you can report a bug using bug-buddy or the GNOME Bugzilla - interface. If you think the problem lies in a FreeBSD port, or + interface. If you think the problem lies in a &os; 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 relevant bug IDs to &email;@FreeBSD.org so we can keep track of known issues. Thanks!

  6. How can I help with the development versions?

    Now that work on &gnomedevelver; has started, we need people to install it, and test things. If you are compiling &gnomedevelver; by hand, be sure to build debugging symbols. Package users will have these symbols already.

  7. -

    What is the current state of development GNOME on FreeBSD?

    +

    What is the current state of development GNOME on &os;?

    -

    We have just cleared out the MarcusCom ports tree after - merging &gnomever; into the FreeBSD ports tree. Stay tuned - for the start of &gnomedevelver; work.

    +

    &gnomever; is the latest version that was merged into the &os; ports tree. + Work is currently underway to make &gnomedevelver; stable.

diff --git a/en_US.ISO8859-1/htdocs/gnome/index.xsl b/en_US.ISO8859-1/htdocs/gnome/index.xsl index 69d7bdc287..6deec9f5e0 100644 --- a/en_US.ISO8859-1/htdocs/gnome/index.xsl +++ b/en_US.ISO8859-1/htdocs/gnome/index.xsl @@ -1,176 +1,176 @@ ]> &title;
&nav.gnome;

FreeBSD GNOME News

Latest update: ,


GNOME Project News

&title;

What is GNOME?

GNOME Logo

GNOME is a complete graphical desktop for X, including everything from a window manager to web browsers, audio players, office programs, and more.

-

The FreeBSD GNOME Project is a team of devoted +

The &os; GNOME Project is a team of devoted developers and users that manage the - integration of GNOME and FreeBSD.

+ integration of GNOME and &os;.

How to install GNOME

The easiest way to install GNOME is to install either of the following ports:

  • x11/gnome2 (the full desktop)
  • x11/gnome2-lite (the minimum desktop environment)

And, as desired, one or all of:

  • x11/gnome2-fifth-toe (common applications)
  • x11/gnome2-power-tools (tools/toys for power users)
  • editors/gnome2-office (office productivity)
  • devel/gnome2-hacker-tools (development tools)

Upgrading to GNOME 2.32?

If you are upgrading from GNOME 2.30 to GNOME 2.32, read the Upgrade FAQ for upgrade instructions.

State of the port

-

GNOME for FreeBSD is currently fully supported on - 8.3, 8-STABLE, 9.0, 9.1, and 9-STABLE, while - 10.0-CURRENT is provided on a best effort basis. - Most of GNOME has been ported to FreeBSD, but there is still - plenty left to be done!

+

GNOME for &os; is currently fully supported on + 8.4, 8-STABLE, 9.1, 9.2, and 9-STABLE, 10.0 and 10-STABLE while + 11.0-CURRENT is provided on a best effort basis. + Work is being done to replace Gnome 2 with Mate and Gnome3. + There is still plenty left to be done!

One stop solution shop!

-

GNOME is simple and easy to build using the FreeBSD ports system, but +

GNOME is simple and easy to build using the &os; ports system, but sometimes things simply go wrong. If GNOME -- or anything that uses GNOME libraries -- is not building the way it should, simply run the gnomelogalyzer.sh tool from the directory of the failed port, and let the gnomelogalyzer figure out what's wrong and how to fix it!

Resources

Related Projects

Search the freebsd-gnome mailing list archives:


 diff --git a/share/xml/release.ent b/share/xml/release.ent index 95031595c1..1c686855d7 100644 --- a/share/xml/release.ent +++ b/share/xml/release.ent @@ -1,86 +1,86 @@ - +