
                                 GARNOME!

   GARNOME -- the bad-ass, bleeding edge GNOME distribution for testers
   and tweakers everywhere -- is finally released unto the teeming masses.
   If you're dying to test the latest GNOME code, but don't want to fall
   into the depraved addictions and co-dependencies of testing from
   anonymous CVS, then GARNOME is for you.

What is GARNOME?
----------------

   It's a bad-ass, bleeding edge GNOME distribution for testers and
   tweakers everywhere. Those not paying attention can stay after class.

   GARNOME is a distribution of GNOME, based on the [1]GAR ports system
   by Nick Moffitt. It builds the latest GNOME Desktop tarball releases,
   and includes extra GNOME 2.x software to provide testers with a
   comfortable desktop environment.

   Join our [2]mailing list! Read the [3]archives!

What do I need to install GARNOME?
----------------------------------

   First you'll have to [4]download GARNOME!

   A sane GNU tool chain (gcc, make, flex, bison, gettext, patch, etc).

   wget, gzip and bzip2.

   The following basic libraries that GNOME depends on. Every
   distribution should have these available or installed already. 

   For starters, you will need a relatively complete X setup.
   The requirements for this vary depending if you are using XFree86
   (4.x.x) or xorg (6.8.x) as part of your setup.
   
     Debian / Ubuntu			Red Hat Linux
     ---------------			-------------
     xlibs-dev [4.x and 6.x]		XFree86-devel [4.x]
     xlibs-static-dev [4.x]		XFree86-libs [4.x]
     libxfixes-dev [6.x]		xorg-x11-devel [6.x]
     libxss-dev [6.x]			xorg-x11-libs [6.x]
     
   Next, if you are using a Linux system with a 2.6.x (or later)
   kernel, you will also need:
     
     Debian / Ubuntu			Red Hat Linux
     ---------------			-------------
     dbus-glib-1-dev			dbus-devel, dbus-glib-devel
     libhal-dev				hal-devel
     libhal-storage-dev

   If you require multimedia support in your install (MP3 playing,
   iPod support or video playing), you will also want:
     
     Debian / Ubuntu			Red Hat Linux
     ---------------			-------------
     libflac-dev			flac-devel				
     libfaad2-dev			faad2-devel			
     liblame-dev			lame-devel
     libid3tag0-dev			libid3tag-devel
     libmad0-dev			libmad-devel (via freshrpms.net)
     libmpeg2-4-dev			mpeg2dec-devel (via freshrpms.net)
     libogg-dev				libogg-devel
     libvisual-dev (via cipherfunk.org) libvisual-devel (via dag.wieers.com) 
     libvorbis-dev			libvorbis-devel
     libxvidcore4-dev			xvidcore-devel (via dag.wieers.com)
   
   At this stage, you should be ready to start building GARNOME
   itself.
   
   For a basic, sane platform/ directory:

     Debian / Ubuntu			Red Hat Linux
     ---------------			-------------
     libpng3-dev			libpng-devel
     libjpeg62-dev			libjpeg-devel
     libtiff4-dev			libtiff-devel
     libncurses5-dev			ncurses-devel
     libpopt-dev			popt
     libgdbm-dev			gdbm-devel
     libbz2-dev, zlib1g-dev		bzip2-devel
     libexpat1-dev			expat-devel
     libsmbclient-dev			samba
     libhermes1-dev or hermes1-dev	Hermes-devel (via freshrpms.net)
     docbook-xml + docbook-xsl		docbook-dtds
     openjade or jade 			openjade

   For other GARNOME directories:

     Debian / Ubuntu			Red Hat Linux
     ---------------			-------------
     binutils-dev			binutils + elfutils-libelf
     libpcre3-dev			pcre-devel
     libaspell-dev			aspell-devel or pspell-devel
     libkrb5-dev			krb5-devel
     libapm-dev				apmd
     libcupsys2-dev			cups-devel
     libexif-dev			libexif-devel
     liblcms1-dev			lcms-devel
     libgpgme-dev			libgpgme-devel + libgpg-error-devel
     libgnutls-dev			gnutls-devel
     libpisock-dev			pilot-link-devel
     libreadline4-dev			readline-devel
     libsensors-dev			lm_sensors-devel
     libldap2-dev			openldap-devel
     libopenh323-dev			openh323-devel
     libpt-dev				pwlib-devel
     libsdl-dev				SDL-devel
     libgcj-dev				libgcj-devel
     libgtkspell-dev			gtkspell-devel
     python2.4-dev			python-devel
     valgrind				valgrind (via dag.wieers.com)


     Thanks to Kevin C. Krinke for providing the original Debian list we 
     based this from.

How do I configure GARNOME?
---------------------------

   All the local settings are kept in gar.conf.mk. Here are the most
   useful ones:

   GARCHIVEDIR: If you've downloaded the tarball collection already,
   point this to the directory your tarballs are in. Example:

     GARCHIVEDIR = /home/pd/src/garnome/DOWNLOAD

   main_prefix: Currently the default install location is $HOME/garnome.
   If you'd prefer to install GARNOME elsewhere, change this entry.
   
   IMPORTANT NOTE: It is NOT advised, or supported to install GARNOME
   as the 'root' user on your system.

   If you would like to build GARNOME so that all of your users can
   use it, please set main_prefix to something sane like  '/opt',
   '/opt/gnome-$VERSION' or '/usr/local/garnome' and then adapt the
   configuration accordingly. Use a dedicated 'build' user rather than
   the root account, who should own this directory. This is the *only*
   step that needs root privileges.
   
   Support questions about installing GARNOME as the 'root' user will
   be discarded.

How do I use GARNOME?
---------------------

   Unpack the tarball, and optionally tweak the settings to your liking.
   The defaults should work without problems, but please refer to the
   'configuration' portion of this document for tips. 

An IMPORTANT note about building as root!
-----------------------------------------
   
   Seriously, building a desktop like GNOME as the root user isn't
   a good idea. 
   
   If your intention is to have all the users on a multiple
   user system using the new desktop, create a dedicated 'build' user who 
   owns the directory you specified for main_prefix in the gar.conf.mk
   file. (see the section entitled "How do I configure GARNOME?" for more
   information on how to do this)
   
   Heed the warning above, it's simpler and quicker to type 'man useradd'
   than it is to re-install your box after a rogue program breaks it.

   You should never build the entire GARNOME tree as 'root', unless you
   really do know what you are doing and there is absolutely no way to
   avoid it.

An IMPORTANT note about bootstrap/
----------------------------------

   The number one question we get asked on the GARNOME list is about the
   contents of the bootstrap/ directory.  For those who don't know, this
   directory contains programs that may or may not be present as part of an
   installed system, but have garballs included for compatibility reasons.
   
   The bootstrap/ directory is for things that fit into three categories:
   
   a) things that your distribution does not ship native packages of
   b) things that your distribution does ship, but ships broken variations
   c) things that are required to run the most recent versions of GNOME
   
   Note from Paul: Often, I get asked: 'Can you ship a kernel/gcc/glibc/X in
   bootstrap/' -- the answer to this is ...
   
   ... ALWAYS GOING TO BE NO! ...
   
   X, for example -- affects the whole of your system, not just GNOME --
   shipping x.org because users would like to have transparent windows in 
   their sessions is not an adequate reason to make the distribution ten
   times the size and further increase it's maintainence overhead. If you'd
   like transparent windowing, i'd suggest upgrading to a distribution that
   already contains x.org, then building GARNOME on that.
   
   [ this has been a public service announcement from Paul's sanity ]
   
   The following systems _need_ things from bootstrap/

   System Type			Requires
   -----------			--------
   Debian <= sid		libiconv
   Mandrake <= 9.0		libiconv
   Mac OS X			dlcompat, libiconv

   The bootstrap/ directory works slightly differently to other directories,
   to use it -- you need to enter each directory you need and type
   'make install'.

   For example, to compile on Mac OS X -- you would type:

   cd bootstrap/dlcompat/
   make install

   (then repeat the process for the other packages you need)

   A rule of thumb to use is: 
   
   'Unless you know you need something in bootstrap/, you don't!'


An IMPORTANT note about Linux, 2.6 kernels and GARNOME features
---------------------------------------------------------------

    Since the release of GNOME 2.8.0, a number of features have been added to 
    the core GNOME desktop that allows enhanced filesystem features, 
    device-management and more.

    The GNOME 2.12.0 release includes even more functionality which relies on
    a recent kernel and associated libraries being in place. In fact
    vast areas of the desktop are now controlled by special daemons that allows
    everything from fine grained access control to network discovery to
    multimedia functionality.

    The downside to this, is some portions of GNOME now depend on a 2.6.x or 
    newer kernel, as well as 'hal', 'dbus' and several other components. 

    If you are running an older distribution, this may mean that random 
    portions of the GARNOME desktop/ directory may not build.

    To fix this, you will need to upgrade to a 2.6.10 (or later) kernel, and 
    compile 'bootstrap/dbus' and 'bootstrap/hal'

Building GARNOME
----------------

   Once you have determined if you need bootstrap/, simply return to the main
   GARNOME directory and type:

   cd desktop/
   make paranoid-install

   That's all there is to it! GARNOME will begin to build and install the
   GNOME Desktop release, and everything it needs immediately.

   If you want to build other meta directories or individual modules, just
   change to the appropriate directory and type 'make paranoid-install' or
   'make install' respectively.

   'paranoid-install' is only available for meta garballs and will stop
   building on the first error. Running 'make install' for a meta garball will
   continue building on errors, trying to build other packages.

   There is a lot of packages included in GARNOME that is not built as part of
   the desktop/ category, including:

   bindings/		GNOME platform bindings collection

   fifth-toe/		A collection of high quality third-party programs 
			designed for your desktop, including Multimedia, 
			Graphics and Internet applications.

   geektoys/		Various extensions to GARNOME that can enhance the 
			usability of your desktop, including new desktop 
			themes and applets that fit into an existing 
			installation.

   hacker-tools/	Debuggers, Interface Designers and Hex Editors, oh my.

   mono/		Mono(tm)

   office/		Parts of the proposed 'GNOME Office' suite, including 
			a spreadsheet application, word processor and a
			database application.

   Two other categories, which GARNOME depends upon internally, contain:
   
   bootstrap/		A collection of libraries/sources that are required to
			build parts of the GNOME desktop, but are not found on
			some older platforms.
			
   freedesktop/		Includes the freedesktop XDG specification, as well as
			sources from other freedesktop.org projects that GNOME
			uses to increase functionality / usability of it's
			product.

How do I start GARNOME once it is installed?
--------------------------------------------

   The easiest way is to create a garnome-session script, and use the
   standard method your distribution provides to launch it when you start
   X. Here's what the script should look like:

     #!/bin/sh
     GARNOME=$HOME/garnome
     PATH=$GARNOME/bin:$GARNOME/sbin:$PATH
     LD_LIBRARY_PATH=$GARNOME/lib:$LD_LIBRARY_PATH
     PYTHONPATH=$GARNOME/lib/python2.4/site-packages
     PKG_CONFIG_PATH=$GARNOME/lib/pkgconfig:/usr/lib/pkgconfig
     XDG_DATA_DIRS=$GARNOME/share
     XDG_CONFIG_DIRS=$GARNOME/etc/xdg
     GDK_USE_XFT=1
     export PATH LD_LIBRARY_PATH PYTHONPATH PKG_CONFIG_PATH GDK_USE_XFT XDG_DATA_DIRS XDG_CONFIG_DIRS
     exec $GARNOME/bin/gnome-session

   Just set the GARNOME variable at the top to wherever you installed
   GARNOME. It will usually be $HOME/garnome, as above.

   If you start X with the startx command you should launch this in
   ~/.xinitrc. If you use the Xsession menu choice in GDM, you should
   launch this in ~/.xsession. Assuming the garnome-session script is in
   your path, both files should look like this:

     #!/bin/sh
     exec garnome-session

   My own startup script is a little bit funkier:

     #!/bin/sh
     xset -solid black
     if [ -e /home/pd/.fonts ]; then
     xset fp+ /home/pd/.fonts/
     xset fp rehash
     fi
     exec /usr/bin/ssh-agent /home/pd/garnome/bin/garnome-session & wmpid=$!
     wait $wmpid

   This sets the background to black so I don't have to look at the ugly
   grey default for very long, sets up old X programs to use all the
   fonts I have in my .fonts directory, and runs garnome-session under
   ssh-agent (very useful if you use ssh keys) and then sits in the
   background waiting for the session to conclude (useful for multiuser
   and terminal based setups).

FAQ
---

    BASIC QUESTIONS:
    ----------------
    
    1. Can I install GARNOME without breaking my current GNOME setup?

       Sure, that's part of what GARNOME is for! By default, it will
       install to ~/garnome/ and not effect any of your existing GNOME
       packages. It may affect your configuration files though, so you
       ought to back them up or use a totally different user to run
       GARNOME.

    2. Can I install GARNOME over the top of my existing GNOME setup?
    
       You could, but you shouldn't! (and we won't support you if you do)
       
       GARNOME isn't a package based setup, it installs from GNOME tarballs
       with patches. If you install GARNOME into /usr (for example), you will
       overwrite your system setup with the software we provide.
       
       All of your configuration will be overwritten, all of your settings
       could vanish, all of the development libraries will be installed and
       you will destroy any knowledge your packaging software (RPM, dpkg, etc)
       has about your setup.
       
    3. How long does GARNOME take to build?

       On a Pentium III 1800, 512MB RAM system, building the GARNOME
       2.8.0 desktop/ directory with time(1) returns:
       real 93m26.111s
       user 48m10.224s
       sys 9m6.119s

       On a Celeron 666 with 128MB RAM, the same install takes:
       real 341m40.180s
       user 225m11.216s
       sys 35m1.111s

    4. Can I speed up my GARNOME build?
    
       Yes.
       
       You can use ccache to speed up your GARNOME builds, although this 
       procedure requires additional disc space in your GARNOME build 
       directory.
       
       Using ccache is a three step task, first you need to install 
       'bootstrap/ccache', then set your cache sizes, then configure your 
       gar.conf.mk file to use the cache.
       
       GARNOME will require a different size cache depending on what parts 
       of it you choose to build, however, for best results -- setting your 
       cache size to 2GB by typing:
       
       ccache -M 2G
       
       Will be sufficently large to build all of the standard platform/ and 
       desktop/ garballs.
       
       Once you have installed the software and set your cache size correctly, 
       open the gar.conf.mk file in the main GARNOME directory and uncomment 
       the lines relating to building with ccache.
       
       note: If you are building bootstrap/mozilla, we recommend you make your 
       cache size 3GB -- otherwise, your cache may resize itself during the 
       build, which may evict some of the more important components of your 
       cache, slowing your build down.

    5. Can I optimize my GARNOME build?
    
       Yes.
       
       Open the gar.conf.mk file in the main GARNOME directory and
       look for the CC, CXX and CFLAGS lines -- uncomment these and
       specify the flags that you need.
       
       note: the best way to get a set of CFLAGS that will work with
       your configuration is to use the cpucaps[7] program from the prompt,
       you should see a line that says:
       
       "Recommended gcc (version) target"
       
       Uncomment and replace the CFLAGS line with the suggestions from that
       line and restart your GARNOME build.
       
    5. How much space does GARNOME require to build?

       On an x86 system, GARNOME 2.12.0 (desktop category and its dependencies)
       requires 2.5GB as build space (plus an additional 1GB if you are
       building bootstrap/), however it only occupies 650MB once installed.
    
    PRE-CONFIGURATION QUESTIONS:
    ----------------------------
    
    1. GARNOME always fails on the checksums, are my tarballs broken?

    Are you using GNU tools? Sometimes Sun's md5sum doesn't agree with
    GARNOME's stored md5sums.
    
    You can change the program used to calculate the md5sum's by editing
    your gar.conf.mk file and altering the $(MD5) variable.

    2. What is bootstrap/ for?

    Please press 'Page Up' a few times and read the section entitled:
    'An IMPORTANT note about bootstrap/'
       
    BUILD QUESTIONS:
    ----------------
    
    1. My build fails with:
    
	"checking mach-o/dyld.h usability... no
	 checking mach-o/dyld.h presence... no
	 checking for mach-o/dyld.h... no
	 configure: error: No dyld.h found, can not continue
	 make[1]: *** [configure-work/main.d/dlcompat-20030629/configure] Error 1"

    You are trying to compile dlcompat from bootstrap/ when you shouldn't be.

    Please press 'Page Up' a few times and read the section entitled:
    'An IMPORTANT note about bootstrap/' -- then type 'make install' from the
    desktop/ directory.

    2. My build fails in platform/glib with:

	"gconvert.c:47:2: #error GNU libiconv not in use but included iconv.h 
	is from libiconv"

    You are trying to compile libiconv from bootstrap/ when you shouldn't be.

    Aside from pressing 'Page Up' a few times and reading the section
    entitled: 'An IMPORTANT note about bootstrap/' -- you have three options:
    
    a) delete iconv.h from your GARNOME prefix and continue your install
    b) ensure your system includes path is before your GARNOME includes path
       (usually not a good idea)
    c) uncomment the libiconv dependancy in the platform/glib Makefile, 
       and 'make clean; make install' (only worth doing if you're on non-GNU
       systems)

    3. My build fails in desktop/control-center with:
    
	"/home/ubuntu/garnome/lib/libgtk-x11-2.0.so: undefined reference to `g_key_file_get_integer'
	/home/ubuntu/garnome/lib/libgnomevfs-2.so: undefined reference to `g_key_file_load_from_file'
	/home/ubuntu/garnome/lib/libgtk-x11-2.0.so: undefined reference to `g_file_set_contents'"
	
    You are trying to compile on a system that includes pesky .la files.
    
    Some distributions install helper files with their development packages
    (Debian, Ubuntu, Arch Linux, earlier Slackware's) that have hardcoded
    references to libraries in system directories. 
    
    Libtool then may choose to use the information from these files instead of
    probing your system for the correct location of your files, which can cause
    some parts of the GNOME build to link against libraries that have been
    supplied with your system, rather than those that work with GARNOME.
    
    A workaround for this issue has been included with 2.12.0, however -- if
    you find that the problem still comes up, please report it as a bug to
    your distribution.
    
    You can also see: 
    
    http://mail.gnome.org/archives/gtk-devel-list/2003-November/msg00107.html
    and: 
    http://lists.x.org/archives/xorg-modular/2005-April/000063.html 
    
    for more information on this issue.
    
    4. My build fails in platform/libgnomeprint with:

	"checking for libgnomecups-1.0 >= 0.1.0... 
	Package libgnomecups-1.0 was not found in the pkg-config search path.
        Perhaps you should add the directory containing `libgnomecups-1.0.pc'
        to the PKG_CONFIG_PATH environment variable
        No package 'libgnomecups-1.0' found"

    If you have CUPS installed as the printing environment on your machine, you
    should install the geektoys/libgnomecups package, which will solve this 
    problem.

    5. My build fails in desktop/epiphany with:

	"configure: error: Library requirements (mozilla-gtkmozembed) not met; 
	consider adjusting the PKG_CONFIG_PATH environment variable if your 
	libraries are in a nonstandard prefix so pkg-config can find them."

    You don't have a suitable version of Mozilla installed on your system, 
    Epiphany and Galeon need Mozilla 1.7 or later to install correctly.

    To solve this issue, you have two options:

    a) install the relevant mozilla development packages for your system and 
       continue your install
    b) uncomment the bootstrap/mozilla dependancy in the desktop/epiphany 
       Makefile, then run 'make clean; make install'

    If you choose option b), then you need to add the mozilla libraries
    installed in $GARNOME/lib/mozilla-<version> to your LD_LIBRARY_PATH,
    otherwise Gaim and Evolution will not compile for you.

    6. My build fails in desktop/nautilus with:
    
        "nautilus-image-properties-view.c:134:96: macro "exif_content_get_value" passed 4 arguments, but takes just 2
	nautilus-image-properties-view.c: In function `exif_content_callback':
	nautilus-image-properties-view.c:134: `exif_content_get_value' undeclared (first use in this function)
	nautilus-image-properties-view.c:134: (Each undeclared identifier is reported only once
	nautilus-image-properties-view.c:134: for each function it appears in.)
	make[6]: *** [nautilus-image-properties-view.lo] Error 1"

    You are probably trying to compile nautilus with the libexif 0.6.x specific 
    patch.

    You should edit the desktop/nautilus Makefile and comment out the PATCHFILES 
    line, before running 'make clean; make install' in the nautilus directory.
 
    7. My build fails in desktop/gnome-games with:
    
        "/usr/bin/ld: cannot find -lguile-ltdl
	collect2: ld returned 1 exit status"
	
	or:
	
	"cscmi.o(.text+0x2b8): In function `add_slot':
	: undefined reference to `SCM_CHARS'
	cscmi.o(.text+0x2de): In function `add_slot':
	: undefined reference to `SCM_CHARS'
	collect2: ld returned 1 exit status"
	
    You are probably trying to compile gnome-games with either a 1.7.x
    'preview release' version of guile, or a version of 1.6.x that has been
    compiled with the '--disable-depreciated' flag.
    
    As stated by the upstream bug[5], to fix this, you will either need to 
    obtain a fixed version of guile from your upstream vendor, or download 
    and compile guile from CVS yourself.
 
    8. My build fails with: 
    
	"/usr/bin/install: cannot stat `./html/index.sgml': No such file 
	or directory"
    
    There are two solutions, in order of "most correct" to "quickest":

    a) Find out why gtkdoc-mkdb is failing. It's usually a b0rked or
       non-existant docbook-dsssl install.
    b) In gnome/category.mk, change --enable-gtk-doc to
       --disable-gtk-doc. Run make clean and make install again.

    If you install the correct software however, or help port our
    documentation from SGML to XML, you will never have this problem
    again. They have to be the best solutions, really. :-)

    9. Scrollkeeper seems to hang when running scrollkeeper-update.

    Yes, it's okay. You just have to wait a while for it to finish
    processing (sometimes a long while). Nothing to be alarmed about.

    10. My gnome-session and Nautilus segfault immediately, what's wrong?

    See [6]bug 70351 at bugzilla.gnome.org.

    11. GARNOME fails to build [insert failure here] on Debian Potato
    
    Mostly, these errors are due to GCC 2.95 incompatibilities.
    
    Again, ranging from "most correct" to "quickest" -- your solutions are:
    
    a) File a bug against the package in question and make sure the 
       [2]Mailing List is on the CC list so that we can pick up any patches
       that may appear.

    b) Install GCC 3.2.3 or later from Debian Testing
    
    12. GARNOME fails to build [insert failure here] on Red Hat 7.3, 8, 9, EL3
    
    There are some components that fail to build in Red Hat, the two main
    issues are:
    
    * OpenSSL / Kerberos
    
    These packages are both affected by Red Hat's packaging of OpenSSL and the
    Kerberos 5 libraries. According to [7]this post -- Red Hat's opinion seems
    to be a need to have these packages require pkg-config. Unfortunately, 
    some earlier OpenSSL installations don't have the .pc support for
    pkg-config niceness, so hacking the GARNOME makefiles to support .pc files
    _might_ work, but you may need to do post-OpenSSL-buggery if your
    distribution is RH7.3, 8 or an unpatched version of 9.
    
    Thus, none of the solutions are particularly "clean" -- but in a pinch:
    
    a) exporting a PKG_CONFIG_PATH variable that points to your GARNOME install
    _before_ the system path ('PKG_CONFIG_PATH=/home/pd/lib/pkgconfig:/usr/lib')
    
    b) Adding the krb5 directory (--with-krb5=/usr/kerberos) 
    to the configure arguments in the Makefile in both the 'office/evolution',
    'office/ximian-connector' and 'fifth-toe/gaim' directories.

    * Binutils (RH9 only)
    
    Red Hat 9 refuses to build 'ghex' because the ghex build doesn't recognize
    'libbfd-2.13.90.0.18.so' as a valid linkable library. Adding a symlink
    from '/usr/lib/libbfd-2.13.90.0.18.so' to '/usr/lib/libbfd.so' is the
    easiest fix for this issue.

    POST-INSTALL QUESTIONS:
    -----------------------

    1. I can see icons on my desktop, but no fonts?
    
    You will need to build freetype, xrender and xft from the bootstrap/
    directory, then restart your GARNOME session to have fonts displayed
    correctly.
    
    2. I can see fonts on my desktop, but no icons?

    You need to build hicolor-icon-theme and shared-mime-info from the
    bootstrap/ directory and add (if it doesn't exist) the XDG_CONFIG_DIRS
    line to your GARNOME startup script.
    
    Note: as of GARNOME 2.10, you need to run some additional commands to
    get this to work as expected -- after adding the required lines,
    run (from the prompt):
	  
    $GARNOME/bin/update-desktop-database
    
    and then:
    
    $GARNOME/bin/update-mime-database $GARNOME/share/mime
    
    Then restart your GARNOME session to get your icons and associations
    back on track.
    
    3. How do I use anti-aliased fonts?

    Set the GDK_USE_XFT environment variable. eg.: export GDK_USE_XFT=1

    4. Where did my evolution/ directory go?

    As part of the upgrade to Evolution 2.2, the import wizard will copy
    your Evolution directory to ~/.evolution.
    
    The GARNOME maintainers recommend you keep a copy of your existing
    ~/evolution directory (if it exists), until you decide that you
    no longer need it.

    5. Who do I talk to about GARNOME?

    Join our [2]mailing list, or visit #garnome on irc.gnome.org.

References
----------

   1. http://www.lnx-bbc.org/garchitecture.html
   2. http://mail.gnome.org/mailman/listinfo/garnome-list
   3. http://mail.gnome.org/archives/garnome-list/
   4. http://cipherfunk.org/garnome/
   5. http://bugzilla.gnome.org/show_bug.cgi?id=164522
   6. http://bugzilla.gnome.org/show_bug.cgi?id=70351
   7. http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=82369
   8. http://members.jcom.home.ne.jp/jacobi/linux/softwares.html

