os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

* Update the list of known issues, and add a new bug

Browse source 
* Mention the gnome_upgrade.sh script as a way to upgrade from GNOME 2.4 to
  2.5.
This commit is contained in:
Joe Marcus Clarke 2004-01-18 21:33:19 +00:00
parent c8e2e3b185
commit d3b8d8cde2
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=19731
1 changed files with 47 additions and 46 deletions
Download patch file Download diff file Expand all files Collapse all files

93
en/gnome/docs/develfaq.sgml
View file

@ -1,6 +1,6 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD: www/en/gnome/docs/develfaq.sgml,v 1.8 2004/01/03 05:59:17 adamw Exp $">
<!ENTITY date "$FreeBSD: www/en/gnome/docs/develfaq.sgml,v 1.9 2004/01/06 17:37:51 marcus Exp $">
<!ENTITY title "FreeBSD GNOME Project: GNOME Development Branch FAQ">
<!ENTITY % gnomeincludes SYSTEM "../includes.sgml"> %gnomeincludes;
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
@ -16,11 +16,11 @@
<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
<li> <a href="#q7">What is the current state of development GNOME on
FreeBSD</a>
</ol>
<h2>Full Text </h2>
<h2>Full Text </h2>
<ol>
<!-- Q1 -->
@ -31,22 +31,22 @@
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
<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
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>
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
unbuildable. The FreeBSD GNOME project pays attention to, but
does not track the alpha quality code.</li>
</ol>
</li>
@ -56,9 +56,9 @@
<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
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>
@ -66,12 +66,12 @@
<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
<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
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>
@ -88,17 +88,21 @@ STRIP=
<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>
<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 useing 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
<a href="/gnome/docs/faq2.html#q6">portupgrade</a> to stay
into your main ports tree. From there, you can download
the <a href="http://www.marcuscom.com/downloads/gnome_upgrade.sh">
gnome_upgrade.sh</a> script to aid in upgrading from GNOME
2.4 to &gnomedevelver;. Once you are running GNOME
&gnomedevelver;, you can use <a
href="/gnome/docs/faq2.html#q6">portupgrade</a> to stay
up-to-date.</p>
<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.
@ -108,7 +112,7 @@ STRIP=
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
<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>
@ -120,13 +124,13 @@ STRIP=
GNOME component, you can report a bug using <b>bug-buddy</b> or
the GNOME <a href="http://bugzilla.gnome.org">BugZilla</a>
interface (<b>NOTE:</b> Evolution's BugZilla interface can be
found <a href="http://bugzilla.ximian.com">here</a>). If you think
the problem lies in a FreeBSD port, or is FreeBSD-specific, send
found <a href="http://bugzilla.ximian.com">here</a>). 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
<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>
@ -139,7 +143,7 @@ STRIP=
many good bugs as possible. We also need people with artistic
skills to create some hot <a href="/gnome/screenshots.html">
screenshots</a>.</p>
<p>If you like coding, and you know Perl, we <em>really</em> need
someone to help in porting
<a href="http://www.gnome.org/projects/gst/index.html">
@ -158,23 +162,17 @@ STRIP=
<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>Development versions of the entire GNOME &gnomedevelver; desktop environment are
available, and they all compile cleanly.</p>
<p>Development versions of the entire GNOME &gnomedevelver; desktop
environment are available, and they all compile cleanly.</p>
<p>Most of the components of <tt>x11/gnome2-fifth-toe</tt> 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.</p>
<p>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.</p>
<p>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.</p>
<p>After updating to libgnomeui-2.5.2, some components (e.g.
gnome-panel) are unable to load their icons.</p>
<p>Desktop icons have read-only emblems. It is said this only
happens for users in the wheel group.</p>
@ -182,8 +180,11 @@ STRIP=
<ul>
<li><a href="http://bugzilla.gnome.org/show_bug.cgi?id=129349">
#129349</a>: [gnome-terminal] keybindings don't work if menu bar
#129349</a>: [gnome-terminal] keybindings don't work if menu bar
isn't visible</li>
<li><a href="http://bugzilla.gnome.org/show_bug.cgi?id=131828">
#131828</a>: [gnome-vfs] file type taking precedence over extension
type</li>
</ul>
</li>
</ol>