diff --git a/en/gnome/docs/develfaq.sgml b/en/gnome/docs/develfaq.sgml index f6c465afdfdd..02f27f33270c 100644 --- a/en/gnome/docs/develfaq.sgml +++ b/en/gnome/docs/develfaq.sgml @@ -1,157 +1,162 @@ - + %gnomeincludes; %includes; ]> &header;
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:
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 homework.
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 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.
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:
CFLAGS= -O -g -pipe STRIP=
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. 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 download the gnome_upgrade29.sh script to aid in upgrading from GNOME &gnomever; 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. 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.
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 (NOTE: Evolution's Bugzilla interface can be 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 &email;@FreeBSD.org so we can keep track of known issues. Thanks!
How can I help with the development versions?-
Hold tight for now until development for &gnomedevelver; - gets under way.+
Start grabbing ports or packages, and let us know how GNOME + &gnomedevelver; handles. We are + looking for build and run problems as well as user + experiences. If you are artistic, start thinking about + FreeBSD GNOME splash screens as well as themes for GNOME + 2.12.
What is the current state of development GNOME on FreeBSD?-
GNOME &gnomever; has just been released, and development on - &gnomedevelver; has not yet begun. Stay tuned.+
The first release of GNOME &gnomedevelver;, 2.11.3, has + been released. Don't be the last thrill-seeker to + upgrade!