diff --git a/en/gnome/docs/Makefile b/en/gnome/docs/Makefile index 0b319b68aa..809afb07e2 100644 --- a/en/gnome/docs/Makefile +++ b/en/gnome/docs/Makefile @@ -1,29 +1,30 @@ -# $FreeBSD: www/en/gnome/docs/Makefile,v 1.25 2008/03/24 05:14:07 marcus Exp $ +# $FreeBSD: www/en/gnome/docs/Makefile,v 1.26 2008/03/30 18:35:28 marcus Exp $ .if exists(../Makefile.conf) .include "../Makefile.conf" .endif .if exists(../Makefile.inc) .include "../Makefile.inc" .endif DOCS= faq2.sgml DOCS+= faq28.sgml DOCS+= faq210.sgml DOCS+= faq212.sgml DOCS+= faq214.sgml DOCS+= faq216.sgml DOCS+= faq218.sgml DOCS+= faq220.sgml DOCS+= faq222.sgml +DOCS+= faq224.sgml DOCS+= gnome_porting.sgml DOCS+= gnome1_porting.sgml DOCS+= gnome2_porting.sgml DOCS+= porting.sgml DOCS+= bugging.sgml DOCS+= volunteer.sgml DOCS+= develfaq.sgml DOCS+= example-Makefile.sgml DOCS+= halfaq.sgml .include "${WEB_PREFIX}/share/mk/web.site.mk" diff --git a/en/gnome/docs/develfaq.sgml b/en/gnome/docs/develfaq.sgml index eb700f9b3a..123f2d46a4 100644 --- a/en/gnome/docs/develfaq.sgml +++ b/en/gnome/docs/develfaq.sgml @@ -1,170 +1,168 @@ - + ]> &header;

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

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 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 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;.
    3. SVN - Often newer-than-new, the SVN trunk 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.

  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 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 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.

    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 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. 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.

  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 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?

    -

    GNOME 2.23.4 is the latest development release, and it is - relatively stable. The only obvious known issue is that - some icons are missing. This is part of an initiative to - clean up the deprecated icons. As the &gnomedevelver; - releases continue, this will gradually be fixed.

    +

    Because of the long ports tree freeze, we have not yet + started work on GNOME &gnomedevelver;. Stay tuned for more + updates.

&footer; diff --git a/en/gnome/docs/faq224.sgml b/en/gnome/docs/faq224.sgml new file mode 100644 index 0000000000..ead5eaab0f --- /dev/null +++ b/en/gnome/docs/faq224.sgml @@ -0,0 +1,148 @@ + + + + +]> + + &header; + +

Contents

+
    +
  1. What is new in GNOME &gnomever;? +
  2. How do I upgrade to GNOME &gnomever;? +
  3. The upgrade failed; what do I do? +
  4. List of known GNOME &gnomever; problems and their solutions +
  5. I have found a bug; whom should I alert? +
  6. I want the fame and glory of the FreeBSD GNOME team! What + can I do to participate? +
+ +

Full Text

+
    + +
  1. +

    What is new in GNOME &gnomever;?

    + +

    Although the canonical summary of new features can be found at + http://library.gnome.org/misc/release-notes/&gnomever;/, + some of the most exciting new features of GNOME &gnomever; are:

    + + + +
    2. + + +
  2. +

    How do I upgrade to GNOME &gnomever;?

    + +

    The answer is relatively simple:

    + +
      +
    1. +

      To build GNOME &gnomever;, you need to obtain the latest + ports tree skeleton. This is most easily accomplished with + portsnap(8) or CVSup. Simply obtain the latest ports tree, and you are + ready to go. Then do the following:

      + 
      +# pkgdb -Ff
+(Answer "yes" to unregister gail while keeping gtk20.)
+(Answer "yes" to unregister fast-user-switch-applet while keeping
+gdm.)
+
+# pkg_deinstall -fO gtkmm-2.12\*
+# portupgrade -aOW
+# portupgrade -f gnome-session
+
      + +

      NOTE: it is recommended to run portupgrade + -a to make sure you get all the necessary ports.

      + +

      If you are a portmaster(8) user, make sure you have + least 1.9 version. Then do the following:

      + + 
      +# pkg_delete -f gtkmm-2.12\*
+# portmaster -a
+# portmaster gnome-session
+
      + +
    +
    3. + + +
  3. +

    The upgrade failed; what do I do?

    + +

    Unfortunately, this is not only possible, it is highly probable. There are many possible + valid GNOME configurations, and even more invalid starting points. If the script fails, + follow the instructions in the error message to let the FreeBSD GNOME team know about the + failure.

    + +

    The majority of build failures will be dependency-related issues. One simple way to resolve + the problem is to remove the offending port, re-run portupgrade or portmaster, and then + reinstall the port when the upgrade process is complete.

    +
    4. + + +
  4. +

    List of GNOME &gnomever; problems and their solutions

    + +

    Although GNOME &gnomever; is certainly the best release to date (of course), there are + a couple regressions that slipped in, both in the GNOME code and in its implementation + within FreeBSD. Some of the more visible issues are:

    + + +
    5. + + +
  5. +

    I have found a bug; whom should I alert?

    + +

    Please read the FreeBSD GNOME Project's + documentation on reporting bugs. +

    +
    6. + + +
  6. +

    I want the fame and glory of being part of the FreeBSD GNOME team! + What can I do to participate?

    + +

    Please read our list of ways + to get involved! +

    +
    7. +
+ + &footer; + + diff --git a/en/gnome/index.xsl b/en/gnome/index.xsl index 4b67448426..eaf7b7228c 100644 --- a/en/gnome/index.xsl +++ b/en/gnome/index.xsl @@ -1,188 +1,188 @@ ]> - + &header1;
&header2;
&nav;

FreeBSD GNOME News

Latest update: ,


GNOME Project News

&header3;

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 developers and users that manage the integration of GNOME and FreeBSD.

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.22?

+

Upgrading to GNOME 2.24?

-

If you are upgrading from GNOME 2.20 to GNOME 2.22, read the +

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

State of the port

GNOME for FreeBSD is currently supported on - 6.3, 6-STABLE, 7.0, 7-STABLE, and 8-CURRENT. + 6.4, 6-STABLE, 7.0, 7.1, 7-STABLE, and 8-CURRENT. Most of GNOME has been ported to FreeBSD, but 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 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: