Added "gnome" virtual appliance

gnome/critical

@@ -0,0 +1,36 @@
+app-editors/nano
+net-misc/openssh
+net-misc/rsync
+net-misc/wget
+sys-kernel/gentoo-sources
+sys-kernel/linux-headers
+sys-devel/gcc
+sys-devel/automake
+sys-devel/bison
+sys-devel/make
+sys-devel/flex
+sys-devel/automake-wrapper
+sys-devel/autoconf-wrapper
+sys-devel/autoconf
+sys-devel/m4
+sys-devel/gcc-config
+sys-devel/libtool
+sys-devel/binutils
+sys-devel/binutils-config
+sys-devel/patch
+sys-devel/gnuconfig
+app-admin/python-updater
+app-admin/perl-cleaner
+sys-apps/man-pages
+sys-apps/man
+sys-apps/file
+sys-apps/less
+sys-apps/texinfo
+sys-apps/busybox
+sys-apps/debianutils
+sys-apps/man-pages-posix
+sys-apps/sandbox
+sys-apps/which
+dev-lang/perl
+sys-devel/libperl
+sys-apps/portage

gnome/custom.conf

@@ -0,0 +1,82 @@
+# GDM Custom Configuration file.
+#
+# This file is the appropriate place for specifying your customizations to the
+# GDM configuration.   If you run gdmsetup, it will automatically edit this
+# file for you and will cause the daemon and any running GDM GUI programs to
+# automatically update with the new configuration.  Not all configuration
+# options are supported by gdmsetup, so to modify some values it may be
+# necessary to modify this file directly by hand.
+#
+# This file overrides the default configuration settings.  These settings 
+# are stored in the GDM System Defaults configuration file, which is found
+# at the following location.
+#
+# /usr/share/gdm/defaults.conf.  
+#
+# This file contains comments about the meaning of each configuration option,
+# so is also a useful reference.  Also refer to the documentation links at
+# the end of this comment for further information.  In short, to hand-edit
+# this file, simply add or modify the key=value combination in the
+# appropriate section in the template below this comment section.
+#
+# For example, if you want to specify a different value for the Enable key
+# in the "[debug]" section of your GDM System Defaults configuration file,
+# then add "Enable=true" in the "[debug]" section of this file.  If the
+# key already exists in this file, then simply modify it.
+#
+# Older versions of GDM used the "gdm.conf" file for configuration.  If your
+# system has an old gdm.conf file on the system, it will be used instead of
+# this file - so changes made to this file will not take effect.  Consider
+# migrating your configuration to this file and removing the gdm.conf file.
+#
+# If you hand edit a GDM configuration file, you can run the following
+# command and the GDM daemon will immediately reflect the change.  Any
+# running GDM GUI programs will also be notified to update with the new
+# configuration.
+#
+# gdmflexiserver --command="UPDATE_CONFIG <configuration key>"
+#
+# e.g, the "Enable" key in the "[debug]" section would be "debug/Enable".
+#
+# You can also run gdm-restart or gdm-safe-restart to cause GDM to restart and
+# re-read the new configuration settings.  You can also restart GDM by sending
+# a HUP or USR1 signal to the daemon.  HUP behaves like gdm-restart and causes
+# any user session started by GDM to exit immediately while USR1 behaves like
+# gdm-safe-restart and will wait until all users log out before restarting GDM.
+#
+# For full reference documentation see the gnome help browser under
+# GNOME|System category.  You can also find the docs in HTML form on
+# http://www.gnome.org/projects/gdm/
+#
+# NOTE: Lines that begin with "#" are considered comments.
+#
+# Have fun!
+
+[daemon]
+
+[security]
+
+[xdmcp]
+Enable=True
+
+[gui]
+
+[greeter]
+
+[chooser]
+
+[debug]
+
+# Note that to disable servers defined in the GDM System Defaults
+# configuration file (such as 0=Standard, you must put a line in this file
+# that says 0=inactive, as described in the Configuration section of the GDM
+# documentation.
+#
+[servers]
+0=inactive
+
+# Also note, that if you redefine a [server-foo] section, then GDM will
+# use the definition in this file, not the GDM System Defaults configuration
+# file.  It is currently not possible to disable a [server-foo] section
+# defined in the GDM System Defaults configuration file.
+#

gnome/package.use

@@ -0,0 +1,20 @@
+app-editors/nano ncurses
+dev-lang/python ssl sqlite threads xml
+sys-kernel/gentoo-sources symlink
+
+# for gnome
+app-text/enchant hunspell
+app-text/poppler cairo
+dev-libs/libxml2 python
+gnome-base/gnome-menus python
+gnome-base/gvfs gdu
+media-libs/libcanberra gtk
+media-libs/swfdec gtk
+net-misc/curl ssl
+sys-apps/dbus X
+sys-apps/parted device-mapper
+sys-auth/consolekit policykit
+sys-fs/udev extras
+x11-libs/cairo svg X
+x11-libs/gtk+ jpeg
+x11-libs/pango X

gnome/postinstall

@@ -0,0 +1,10 @@
+#!/bin/sh
+
+CHROOT="$1"
+APPLIANCE="`dirname $0`"
+
+rm -f "${CHROOT}"/var/lib/dbus/machine-id
+cp "${APPLIANCE}"/custom.conf "${CHROOT}"/etc/X11/gdm/custom.conf
+
+chroot "${CHROOT}" rc-update add hald default
+echo 'gdm &>/dev/null' >> "${CHROOT}"/etc/conf.d/local.start

gnome/preinstall

@@ -0,0 +1,11 @@
+#!/bin/sh
+
+CHROOT="$1"
+
+# totem gst-inspect requires a machine id (generated by dbus). we
+# don't have one yet because we are in a virgin chroot. fake one
+mkdir -p "${CHROOT}/var/lib/dbus"
+echo 1234567890abcdef1234567890abcdef > "${CHROOT}"/var/lib/dbus/machine-id
+
+# argh, something depends on pkgconfig but it's not in it's deps
+chroot "${CHROOT}" emerge -1n dev-util/pkgconfig

gnome/world

@@ -0,0 +1,3 @@
+gnome-base/gnome
+media-fonts/dejavu
+media-fonts/freefont-ttf