b299fd0772
* Add instructions on upgrading from 2.14 to 2.16 The bulk of the 2.16 documentation will be added with 2.16 is committed to ports.
176 lines
7.7 KiB
Text
176 lines
7.7 KiB
Text
<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [
|
|
<!ENTITY base CDATA "../..">
|
|
<!ENTITY date "$FreeBSD: www/en/gnome/docs/develfaq.sgml,v 1.44 2006/08/19 21:20:35 hrs Exp $">
|
|
<!ENTITY title "FreeBSD GNOME Project: GNOME Development Branch FAQ">
|
|
<!ENTITY % navinclude.gnome "INCLUDE">
|
|
]>
|
|
<html>
|
|
&header;
|
|
|
|
<h2>Contents</h2>
|
|
<ol>
|
|
<li> <a href="#q1">What are development versions of GNOME all about?</a>
|
|
<li> <a href="#q2">Should I track development versions?</a>
|
|
<li> <a href="#q3">How do I obtain development versions of GNOME stuff?</a>
|
|
<li> <a href="#q4">How do I keep everything up-to-date and in sync?</a>
|
|
<li> <a href="#q5">What should I do when something does not work?</a>
|
|
<li> <a href="#q6">How can I help with the development versions?</a>
|
|
<li> <a href="#q7">What is the current state of development GNOME on
|
|
FreeBSD</a>
|
|
</ol>
|
|
|
|
<h2>Full Text </h2>
|
|
|
|
<ol>
|
|
<!-- Q1 -->
|
|
<li style="padding-bottom: 0.5em"><a name="q1"></a>
|
|
<p><b>What are development versions of GNOME all about?</b></p>
|
|
<!-- A1 -->
|
|
<p>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:</p>
|
|
<ol>
|
|
<li><b>STABLE</b> - 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;.</li>
|
|
<li><b>DEVELOPMENT</b> - 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
|
|
about the development branch. The current development branch
|
|
is GNOME &gnomedevelver;.</li>
|
|
<li><b>CVS</b> - 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
|
|
does not track the alpha quality code.</li>
|
|
</ol>
|
|
</li>
|
|
|
|
<!-- Q2 -->
|
|
<li style="padding-bottom: 0.5em"><a name="q2"></a>
|
|
<p><b>Should I track GNOME development versions?</b></p>
|
|
<!-- A2 -->
|
|
<p>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.</p>
|
|
</li>
|
|
|
|
<!-- Q3 -->
|
|
<li style="padding-bottom: 0.5em"><a name="q3"></a>
|
|
<p><b>How do I obtain the development versions of GNOME stuff?</b></p>
|
|
<!-- A3 -->
|
|
<p><a href="mailto:marcus@FreeBSD.org">Marcus</a> 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
|
|
<a href="http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi">http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi</a>.
|
|
</p>
|
|
|
|
<p>During the development cycle, FreeBSD-specific caveats and
|
|
other useful information will be sent to <a
|
|
href="mailto:marcuscom-devel@marcuscom.com">
|
|
marcuscom-devel@marcuscom.com</a>. If you are tracking
|
|
the GNOME development branch, you <b>must</b> <a
|
|
href="http://www.marcuscom.com/mailman/listinfo/marcuscom-devel">
|
|
subscribe</a> to this list. You should also consider <a
|
|
href="http://lists.freebsd.org/mailman/listinfo/freebsd-gnome">
|
|
subscribing</a> to <a
|
|
href="mailto:&email;@FreeBSD.org">&email;@FreeBSD.org</a>.</p>
|
|
|
|
<p>In order to help with bug reports, be sure to add the following
|
|
to <tt>/etc/make.conf</tt> so that gdb back traces contain
|
|
useful information:</p>
|
|
<pre>
|
|
CFLAGS= -O -g -pipe
|
|
STRIP=
|
|
</pre>
|
|
</li>
|
|
|
|
<!-- Q4 -->
|
|
<li style="padding-bottom: 0.5em"><a name="q4"></a>
|
|
<p><b>How do I keep everything up-to-date and in sync?</b></p>
|
|
<!-- A4 -->
|
|
<p>The short answer is that you need to use the <tt>marcusmerge</tt>
|
|
script to merge the development tree with the FreeBSD ports tree.
|
|
The <tt>marcusmerge</tt> script is available
|
|
<a href="http://www.marcuscom.com/downloads/marcusmerge">
|
|
here</a>, and a man page on using the script is available
|
|
<a href="http://www.marcuscom.com/marcusmerge.8.html">
|
|
here</a>. This script will merge the development ports tree
|
|
into your main ports tree. From there, you can use
|
|
<tt>portupgrade</tt> to upgrade from &gnomever; to &gnomedevelver;
|
|
and stay up-to-date afterwards. <b>NOTE:</b> if this is a
|
|
first-time upgrade from &gnomever; to &gnomedevelver; you
|
|
must run a special <tt>portupgrade</tt> command to account
|
|
for the move from <tt>X11BASE</tt> to <tt>LOCALBASE</tt>:</p>
|
|
|
|
<pre>
|
|
portupgrade -rf glib-2\* cairo gnome-doc-utils gnome-mime-data gnome-audio
|
|
</pre>
|
|
|
|
<p>The long answer is that keeping up-to-date with the GNOME
|
|
development branch is complicated. Sometimes components change
|
|
in a way that makes <tt>portupgrade</tt> fail, or causes strange end results.
|
|
If you plan to track the development branch, it is a good idea
|
|
to join the
|
|
<a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-gnome">
|
|
freebsd-gnome</a> mailing list, as well as to join the
|
|
<em>#freebsd-gnome</em> IRC channel on FreeNode (<tt>irc.freenode.net</tt>).</p>
|
|
|
|
<p>If all of this sounds scary, or you need a desktop that
|
|
"Just Works," you should stick with the stable GNOME branch.</p>
|
|
</li>
|
|
|
|
<!-- Q5 -->
|
|
<li style="padding-bottom: 0.5em"><a name="q5"></a>
|
|
<p><b>What should I do when something does not work?</b></p>
|
|
<!-- A5 -->
|
|
<p>It depends. If you think the problem is truly a bug with the
|
|
GNOME component, you can report a bug using <b>bug-buddy</b> or
|
|
the GNOME <a href="http://bugzilla.gnome.org">Bugzilla</a>
|
|
interface. If you think the problem lies in a FreeBSD port, or
|
|
is FreeBSD-specific, send email to
|
|
<a href="mailto:&email;@FreeBSD.org">&email;@FreeBSD.org</a>,
|
|
or report the problem on the <em>#freebsd-gnome</em> IRC
|
|
channel on FreeNode.</p>
|
|
|
|
<p>Please forward all GNOME/Ximian bug IDs to
|
|
<a href="mailto:&email;@FreeBSD.org">&email;@FreeBSD.org</a>
|
|
so we can keep track of known issues. Thanks!</p>
|
|
</li>
|
|
|
|
<!-- Q6 -->
|
|
<li style="padding-bottom: 0.5em"><a name="q6"></a>
|
|
<p><b>How can I help with the development versions?</b></p>
|
|
<!-- A6 -->
|
|
<p>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, please start submitting
|
|
splash screens and themes for 2.16. We are also looking for
|
|
some screenshots that show off some of the new features of
|
|
GNOME 2.16.</p>
|
|
</li>
|
|
|
|
<!-- Q7 -->
|
|
<li style="padding-bottom: 0.5em"><a name="q7"></a>
|
|
<p><b>What is the current state of development GNOME on FreeBSD?</b></p>
|
|
<!-- A7 -->
|
|
<p>GNOME 2.16 release is available and being tested.
|
|
As usual, test ports and
|
|
<a href="faq2.html#q21">packages</a>, and report any
|
|
problems to the authorities listed above.</p>
|
|
|
|
</li>
|
|
</ol>
|
|
&footer;
|
|
</body>
|
|
</html>
|