Difference between pages "Metro" and "GNOME First Steps"

(Difference between pages)
 
(GNOME 3.14 from a clean install)
 
Line 1: Line 1:
{{#layout:doc}}{{#widget:AddThis}}[[Metro]] is the build system for Funtoo Linux and [[Gentoo Linux]] stages. It automates the bootstrapping process.
+
=== What is GNOME? ===
  
This tutorial will take you through installing, setting up and running [[Metro]].
+
"GNOME 3 is an easy and elegant way to use your computer. It is designed to put you in control and bring freedom to everybody. GNOME 3 is developed by the GNOME community, a diverse, international group of contributors that is supported by an independent, non-profit foundation." — [http://gnome.org GNOME]
  
These other Metro documents are also available:
+
=== Prerequisites ===
  
{{#ask: [[Category:Metro]]
+
==== From a Clean Install ====
|format=ul
+
}}
+
  
= Preface =
+
Ensure that the [[X Window System]] is installed.
  
== How Metro Works ==  
+
=== Preparing to emerge ===
  
Metro is the Funtoo Linux automated build system, and is used to build Funtoo Linux stage tarballs.
+
To get your system ready to emerge gnome, first set your system flavor to desktop, and enable the gnome profile mix-in. To accomplish this, do the following:
 +
{{console|recipe=setup,setup-light|desc=Set profile|body=
 +
# ##i##eselect profile set-flavor funtoo/1.0/linux-gnu/flavor/desktop
 +
# ##i##eselect profile add funtoo/1.0/linux-gnu/mix-ins/gnome
 +
}}
  
[[Metro]] cannot create a stage tarball out of thin air. To build a new stage tarball, [[Metro]] must use an existing, older stage tarball called a "seed" stage. This seed stage typically is used as the ''build environment'' for creating the stage we want.
+
By enabling the gnome mix-in, various USE and other settings will be optimized to provide you with a pain-free GNOME installation experience.
  
[[Metro]] can use two kinds of seed stages. Traditionally, [[Metro]] has used a stage3 as a seed stage. This stage3 is then used to build a new stage1, which in turn is used to build a new stage2, and then a new stage3. This is generally the most reliable way to build [[Gentoo Linux]] or Funtoo Linux, so it's the recommended approach.
+
=== Emerging ===
{{fancyimportant|'''After switching metro builds to Funtoo profile, Gentoo stages are no longer provided'''!}}
+
  
== Seeds and Build Isolation ==
+
You are provided with two packages that will pull in this desktop environment:
  
Another important concept to mention here is something called ''build isolation''. Because [[Metro]] creates an isolated build environment, and the build environment is explicitly defined using existing, tangible entities -- a seed stage and a portage snapshot -- you will get consistent, repeatable results. In other words, the same seed stage, portage snapshot and build instructions will generate an essentially identical result, even if you perform the build a month later on someone else's workstation.
+
* ''gnome''
  
== Local Build ==
+
{{fancynote|This is the "whole shabang" - pulls in a range of applications made for the gnome desktop environment including a few games, an archive manager, a system monitor, a web browser, a terminal, etc.}}
  
Say you wanted to build a new <tt>pentium4</tt> stage3 tarball. The recommended method of doing this would be to grab an existing <tt>pentium4</tt> stage3 tarball to use as your seed stage. [[Metro]] will be told to use this existing <tt>pentium4</tt> stage3 to build a new stage1 for the same <tt>pentium4</tt>. For this process, the generic <tt>pentium4</tt> stage3 would provide the ''build environment'' for creating our new stage1. Then, the new stage1 would serve as the build environment for creating the new <tt>pentium4</tt> stage2. And the new <tt>pentium4</tt> stage2 would serve as the build environment for creating the new <tt>pentium4</tt> stage3.
+
* ''gnome-light''
  
In the [[Metro]] terminology this is called a '''local build''', which means a stage3 of a given architecture is used to seed a brand new build of the same architecture. Incidentally this will be the first exercise we are going to perform in this tutorial.
+
{{fancynote|As the name implies, this pulls in the base minimal you need to get a functioning GNOME Desktop Environment.}}
  
A week later, you may want to build a brand new <tt>pentium4</tt> stage3 tarball. Rather than starting from the original <tt>pentium4</tt> stage3 again, you'd probably configure [[Metro]] to use the most-recently-built <tt>pentium4</tt> stage3 as the seed. [[Metro]] has built-in functionality to make this easy, allowing it to easily find and track the most recent stage3 seed available.
+
==== GNOME 3.14 from a clean install ====
  
== Remote Build ==  
+
===== gnome =====
  
[[Metro]] can also perform '''remote build''', where a stage3 of a different, but binary compatible, architecture is used as a seed to build a different architecture stage3. Consequentiality the second exercise we are going to perform in this tutorial will be to build a <tt>core2 32bit</tt> stage3 tarball from the <tt>pentium4</tt> stage3 tarball we have just built.
+
To emerge ''gnome'' run the following command
  
TODO: add caveats about what archs can be seeded and what can be not (maybe a table?)
+
{{console|desc=Emerging GNOME|body=
 +
# ##i## emerge gnome
 +
}}
  
== Tailored Build ==  
+
===== gnome-light =====
  
Last, it's also worthy noting that both in <tt>local</tt> and <tt>remote builds</tt>, [[Metro]] can be configured to add and/or remove individual packages to the final tarball.
+
To emerge ''gnome-light'' run the following command
Let's say you can't live without <tt>app-misc/screen</tt>, at the end of this tutorial, we will show how to have your tailored stage3 to include it.
+
  
== Installing Metro ==
+
{{console|recipe=setup-light|desc=Emerging a minimal GNOME environment (alternative)|body=
 +
# ##i## emerge gnome-light
 +
}}
  
'''The recommended and supported method''' is to use the Git repository of [[Metro]].
+
==== Upgrading from GNOME 3.12 ====
  
Ensure that {{Package|dev-vcs/git}} and {{Package|dev-python/boto}} (optional; required for EC2 support) are installed on your system:
+
To update either ''gnome'' or ''gnome-light'' run the following command:
  
<console>
+
{{console|body=
# ##i##emerge dev-vcs/git
+
# ##i## emerge -vauDN world
# ##i##emerge dev-python/boto
+
</console>
+
 
+
Next, clone the master git repository as follows:
+
 
+
<console>
+
# ##i##cd /root
+
# ##i##git clone git://github.com/funtoo/metro.git
+
# ##i##cp /root/metro/metro.conf ~/.metro
+
</console>
+
 
+
You will now have a directory called <tt>/root/metro</tt> that contains all the [[Metro]] source code.
+
 
+
Metro is now installed. It's time to customize it for your local system.
+
 
+
= Configuring Metro =
+
 
+
{{Note|Metro is not currently able to build Gentoo stages. See {{Bug|FL-901}}.}}
+
 
+
[[User:Drobbins|Daniel Robbins]] maintains [[Metro]], so it comes pre-configured to successfully build [[Funtoo Linux]] releases. Before reading further, you might want to customize some basic settings like the number of concurrent jobs to fit your hardware's capabilities or the directory to use for produced stage archives. This is accomplished by editing <tt>~/.metro</tt> which is the [[Metro]]'s master configuration file.
+
 
+
Please note that <code>path/install</code> must point to where metro was installed. Point <code>path/distfiles</code> to where your distfiles reside. Also set <code>path/mirror/owner</code> and <code>path/mirror/group</code> to the owner and group of all the files that will be written to the build repository directory, which by default (as per the configuration file) is at <code>/home/mirror/funtoo</code>. The cache directory normally resides inside the temp directory -- this can be modified as desired. The cache directory can end up holding many cached .tbz2 packages, and eat up a lot of storage. You may want to place the temp directory on faster storage, for faster compile times, and place the cache directory on slower, but more plentiful storage.
+
 
+
{{file|name=.metro|desc=Metro configuration|body=
+
# Main metro configuration file - these settings need to be tailored to your install:
+
 
+
[section path]
+
install: /root/metro
+
tmp: /var/tmp/metro
+
cache: $[path/tmp]/cache
+
distfiles: /var/src/distfiles
+
work: $[path/tmp]/work/$[target/build]/$[target/name]
+
 
+
[section path/mirror]
+
 
+
: /home/mirror/funtoo
+
owner: root
+
group: repomgr
+
dirmode: 775
+
 
+
[section portage]
+
 
+
MAKEOPTS: auto
+
 
+
[section emerge]
+
 
+
options: --jobs=4 --load-average=4 --keep-going=n
+
 
+
# This line should not be modified:
+
[collect $[path/install]/etc/master.conf]
+
 
}}
 
}}
 +
=== Subsystems ===
  
== Arch and Subarch ==
+
==== Bluetooth ====
  
In the following example we are creating a pentium4 stage 3 compiled for x86-32bit binary compatibility. Pentium4 is a subarch of the x86-32bit architecture. Once you have metro installed you may find a full list of each subarch in your <tt>/root/metro/subarch</tt> directory each subarch will have the file extension .spec
+
For bluetooth support, ensure that:
Example:
+
<console>
+
###i## ls /root/metro/subarch
+
# ls subarch/
+
amd64-bulldozer-pure64.spec  armv7a.spec          core-avx-i.spec        i686.spec        pentium.spec
+
amd64-bulldozer.spec        armv7a_hardfp.spec  core2_32.spec          k6-2.spec        pentium2.spec
+
amd64-k10-pure64.spec        athlon-4.spec        core2_64-pure64.spec    k6-3.spec        pentium3.spec
+
amd64-k10.spec              athlon-mp.spec      core2_64.spec          k6.spec          pentium4.spec
+
amd64-k8+sse3.spec          athlon-tbird.spec    corei7-pure64.spec      native_32.spec    pentiumpro.spec
+
amd64-k8+sse3_32.spec        athlon-xp.spec      corei7.spec            native_64.spec    prescott.spec
+
amd64-k8-pure64.spec        athlon.spec          generic_32.spec        niagara.spec      ultrasparc.spec
+
amd64-k8.spec                atom_32.spec        generic_64-pure64.spec  niagara2.spec    ultrasparc3.spec
+
amd64-k8_32.spec            atom_64-pure64.spec  generic_64.spec        nocona.spec      xen-pentium4+sse3.spec
+
armv5te.spec                atom_64.spec        generic_sparcv9.spec    opteron_64.spec  xen-pentium4+sse3_64.spec
+
armv6j.spec                  btver1.spec          geode.spec              pentium-m.spec
+
armv6j_hardfp.spec          btver1_64.spec      i486.spec              pentium-mmx.spec
+
</console>
+
  
= First stages build (local build) =
+
# Bluetooth support is enabled in your kernel (using modules is fine).
 +
# Your bluetooth hardware is turned on.
 +
# Add the <code>bluetooth</code> startup script to the default runlevel, and start it.
  
To get this all started, we need to bootstrap the process by downloading an initial seed stage3 to use for building and place it in its proper location in <tt>/home/mirror/funtoo</tt>, so that [[Metro]] can find it. We will also need to create some special &quot;control&quot; files in <tt>/home/mirror/funtoo</tt>, which will allow [[Metro]] to understand how it is supposed to proceed.
+
This can be done as follows:
 
+
== Step 1: Set up pentium4 repository (local build) ==
+
 
+
Assuming we're following the basic steps outlined in the previous section, and building an unstable funtoo (<tt>funtoo-current</tt>) build for the <tt>pentium4</tt>, using a generic <tt>pentium4</tt> stage3 as a seed stage, then here the first set of steps we'd perform:
+
  
 
<console>
 
<console>
# ##i##install -d /home/mirror/funtoo/funtoo-current/x86-32bit/pentium4
+
# ##i##rc-update add bluetooth default
# ##i##install -d /home/mirror/funtoo/funtoo-current/snapshots
+
# ##i##rc
# ##i##cd /home/metro/mirror/funtoo/funtoo-current/x86-32bit/pentium4
+
# ##i##install -d 2011-12-13
+
# ##i##cd 2011-12-13
+
# ##i##wget -c http://ftp.osuosl.org/pub/funtoo/funtoo-current/x86-32bit/pentium4/2011-12-13/stage3-pentium4-funtoo-current-2011-12-13.tar.xz
+
# ##i##cd ..
+
# ##i##install -d .control/version
+
# ##i##echo "2011-12-13" > .control/version/stage3
+
# ##i##install -d .control/strategy
+
# ##i##echo local >  .control/strategy/build
+
# ##i##echo stage3 > .control/strategy/seed
+
 
</console>
 
</console>
  
OK, let's review the steps above. First, we create the directory <tt>/home/mirror/funtoo/funtoo-current/x86-32bit/pentium4</tt>, which is where Metro will expect to find unstable <tt>funtoo-current</tt> pentium4 builds -- it is configured to look here by default. Then we create a specially-named directory to house our seed x86 stage3. Again, by default, Metro expects the directory to be named this way. We enter this directory, and download our seed x86 stage3 from funtoo.org. Note that the <tt>2010-12-24</tt> version stamp matches. Make sure that your directory name matches the stage3 name too. Everything has been set up to match Metro's default filesystem layout.
+
Once this is done, you should now be able to navigate to ''Settings'' -> ''Bluetooth'' and turn bluetooth on. The icon next to devices should now animate and you should be able to discover and add devices such as keyboards.
  
Next, we go back to the <tt>/home/mirror/metro/funtoo-current/x86-32bit/pentium4</tt> directory, and inside it, we create a <tt>.control</tt> directory. This directory and its subdirectories contain special files that Metro references to determine certain aspects of its behavior. The <tt>.control/version/stage3</tt> file is used by Metro to track the most recently-built stage3 for this particular build and subarch. Metro will automatically update this file with a new version stamp after it successfully builds a new stage3. But because Metro didn't actually ''build'' this stage3, we need to set up the <tt>.control/version/stage3</tt> file manually. This will allow Metro to find our downloaded stage3 when we set up our pentium4 build to use it as a seed. Also note that Metro will create a similar <tt>.control/version/stage1</tt> file after it successfully builds an pentium4 funtoo-current stage1.
+
{{Note|1=
 +
Additional kernel drivers may need to be enabled for certain input devices. For example, for the bluetooth Apple Magic Trackpad, the following option must be enabled in your kernel:
  
We also set up <tt>.control/strategy/build</tt> and <tt>.control/strategy/seed</tt> files with values of <tt>local</tt> and <tt>stage3</tt> respectively. These files define the building strategy Metro will use when we build pentium4 funtoo-current stages. With a build strategy of <tt>local</tt>, Metro will source its seed stage from funtoo-current pentium4, the current directory. And with a seed strategy of <tt>stage3</tt>, Metro will use a stage3 as a seed, and use this seed to build a new stage1, stage2 and stage3.
+
{{kernelop|title=Device Drivers,HID support,HID bus support,Special HID drivers|desc=
 +
<M> Apple Magic Mouse/Trackpad multi-touch support
 +
}}}}
  
== Step 2: Building the pentium4 stages ==
+
==== Printing ====
  
Incidentally, if all you wanted to do at this point was to build a new pentium4 funtoo-current stage1/2/3 (plus openvz and vserver templates). You would begin the process by typing:
+
To enable printing support, add <code>cupsd</code> to the default runlevel:
  
 
<console>
 
<console>
# ##i##cd /root/metro
+
# ##i##rc-update add cupsd default
# ##i##scripts/ezbuild.sh funtoo-current pentium4
+
# ##i##rc
 
</console>
 
</console>
  
If you have a slow machine, it could take several hours to be completed because several "heavy" components like gcc or glibc have to be recompiled in each stage. Once a stage has been successfully completed, it is placed in the <tt>"${METRO_MIRROR}/funtoo-current/x32-bit/pentium4/YYYY-MM-DD"</tt> subdirectory, where <tt>YYYY-MM-DD</tt> is today's date at the time the <tt>ezbuild.sh</tt> script was started or the date you put on the ezscript.sh command line.
+
You should now be able to navigate to ''Settings'' -> ''Printers'' and add printers to your system, and print.
  
= Building for another binary compatible architecture (remote build) =
+
==== Scanning ====
  
As written above, [[Metro]] is able to perform '''remote build''' building different architecture stage3 from a binary compatible seeding stage3 (e.g. using a pentium4 stage3 to seed a <tt>Intel Core2 32bits</tt> stage3).  
+
To enable scanning support, add your user account to the <code>lp</code> group. This will allow your user to access the USB scanner.
  
In the Metro terminology this is called a '''remote build''' (a stage 3 of a different, but binary compatible, architecture is used as a seed).
+
Then, <code>emerge xsane</code>, and run it. It should be able to access your scanner.
What's not compatible? You can't use a <tt>Sparc</tt> architecture to generate an <tt>x86</tt> or <tt>ARM</tt> based stage and vice-versa. If you use a 32bit stage then you don't want to seed a 64bit build from it. Be sure that you are using a stage from the same architecture that you are trying to seed. Check [http://ftp.osuosl.org/pub/funtoo/funtoo-current/ Funtoo-current FTP Mirror] for a stage that is from the same Architecture that you will be building.
+
  
{{Note|Often, one build (ie. funtoo-current) can be used as a seed for another build such as funtoo-stable. However, hardened builds require hardened stages as seeds in order for the build to complete successfully.}}
+
=== Finishing Touches ===
  
== Step 1: Set up Core_2 32bit repository ==
+
==== X ====
  
In this example, we're going to use this pentium4 funtoo-current stage3 to seed a new Core_2 32bit funtoo-current build. To get that done, we need to set up the pentium4 build directory as follows:
+
===== Setting up xdm (GUI log-in) =====
  
<console>
+
Typically, you will want to use <code>gdm</code>, the GNOME display manager, to log in to GNOME. This will allow you to log in graphically, rather than using the text console.
# ##i## cd /home/mirror/funtoo/funtoo-current/x86-32bit
+
# ##i##install -d core2_32
+
# ##i##cd core2_32
+
# ##i##install -d .control/strategy
+
# ##i##echo remote > .control/strategy/build
+
# ##i##echo stage3 > .control/strategy/seed
+
# ##i##install -d .control/remote
+
# ##i##echo funtoo-current > .control/remote/build
+
# ##i##echo x86-32bit > .control/remote/arch_desc
+
# ##i##echo pentium4 > .control/remote/subarch
+
</console>
+
  
The steps we follow are similar to those we performed for a ''local build'' to set up our pentium4 directory for local build. However, note the differences. We didn't download a stage, because we are going to use the pentium4 stage to build a new Core_2 32bit stage. We also didn't create the <tt>.control/version/stage{1,3}</tt> files because Metro will create them for us after it successfully builds a new stage1 and stage3. We are still using a <tt>stage3</tt> seed strategy, but we've set the build strategy to <tt>remote</tt>, which means that we're going to use a seed stage that's not from this particular subdirectory. Where are we going to get it from? The <tt>.control/remote</tt> directory contains this information, and lets Metro know that it should look for its seed stage3 in the <tt>/home/mirror/funtoo/funtoo-current/x86-32bit/pentium4</tt> directory. Which one will it grab? You guessed it -- the most recently built ''stage3'' (since our seed strategy was set to <tt>stage3</tt>) that has the version stamp of <tt>2010-12-24</tt>, as recorded in <tt>/home/mirror/funtoo-current/x86-32bit/pentium4/.control/version/stage</tt>. Now you can see how all those control files come together to direct Metro to do the right thing.
+
To enable gdm, edit <code>/etc/conf.d/xdm</code> and set <code>DISPLAYMANAGER</code> to <code>gdm</code> instead of <code>xdm</code>. Then, perform the following steps to add <code>xdm</code> to the default runlevel, and have it start automatically from now on when your system starts:
  
{{Note|<code>arch_desc</code> should be set to one of: <code>x86-32bit</code>, <code>x86-64bit</code> or <code>pure64</code> for PC-compatible systems. You must use a 32-bit build as a seed for other 32-bit builds, and a 64-bit build as a seed for other 64-bit builds.}}
+
{{Note|Funtoo's <code>/etc/init.d/xdm</code> initscript has been modified to start the requisite services <code>dbus</code>, <code>openrc-settingsd</code> and <code>consolekit</code> prior to starting <code>gdm</code>.}}
  
== Step 2: Building the Core_2 32bit stages ==
+
{{console|recipe=setup|desc=Enable the GNOME display manager|body=
 +
# ##i## rc-update add xdm default
 +
}}
  
Now, you could start building your new Core_2 32bit stage1/2/3 (plus openvz and vserver templates) by typing the following:
+
Then, if you want to start it now do:
  
<console>
+
{{console|body=
# ##i##/root/metro/scripts/ezbuild.sh funtoo-current core2_32
+
# ##i##rc
</console>
+
}}
  
In that case, the produced stages are placed in the <tt>/home/mirror/funtoo/funtoo-current/x32-bit/core2_32/YYYY-MM-DD</tt> subdirectory.
+
But you should reboot to avoid having an open login terminal.
  
== Step 3: The Next Build ==
+
===== Setting up xinitrc (text log-in) =====
  
At this point, you now have a new Core_2 32bit stage3, built using a "remote" pentium4 stage3. Once the first remote build completes successfully, metro will automatically change <code>.control/strategy/build</code> to be <code>local</code> instead of <code>remote</code>, so it will use the most recently-built Core_2 32bit stage3 as a seed for any new Core_2 32bit builds from now on.
+
Adding the following to your <code>~/.xinitrc</code> file is sufficient:
  
= Build your own tailored stage3 =
+
<pre>
 +
# Fix Missing Applications in Gnome
 +
export XDG_MENU_PREFIX=gnome-
  
Metro can be easily configured for building custom stage3 by including additional packages. Edit the following configuration file <tt>/root/metro/etc/builds/funtoo-current/build.conf</tt>:
+
# Properly Launch the Desired X Session
{{file|name=funtoo-current/build.conf|body=
+
exec ck-launch-session gnome-session
[collect ../../fslayouts/funtoo/layout.conf]
+
</pre>
  
[section release]
+
Additionaly, if you need support for different input sources, there is no longer a need to configure IBus or SCIM in your <code>.xinitrc</code> file as GNOME uses IBus natively. Simply configure it in the Control Center under Region & Language.
  
author: Daniel Robbins <drobbins@funtoo.org>
+
=== Automatically Starting Applications at Login ===
  
[section target]
+
When using an old-fashioned <code>.xinitrc</code>, starting up applications when X starts is relatively easy. When using GDM, this can still be accomplished, by using the <code>~/.xprofile</code> file. Here's my sample <code>.xprofile</code> to start <code>xflux</code> to dim the screen at night:
  
compression: xz
+
<pre>
 +
xflux -z 87107
 +
</pre>
  
[section portage]
+
{{Note|Remember to add a <code>&</code> at the end of any command that doesn't return to the shell prompt after running.}}
  
FEATURES:
+
=== games ===
SYNC: $[snapshot/source/remote]
+
Gnome has several games that can be added on to your install.  By default most games are not included in gnome's emerge.
USE:
+
  
[section profile]
+
Users wishing to play games need to be added to the games group:
 +
{{console|body=###i## gpasswd -a $USER games}}
  
format: new
+
game list:
path: gentoo:funtoo/1.0/linux-gnu
+
;gnome-sudoku
arch: $[:path]/arch/$[target/arch_desc]
+
;gnome-mastermind
build: $[:path]/build/current
+
;gnome-nibbles
flavor: $[:path]/flavor/core
+
;gnome-robots
mix-ins:
+
;gnome-chess
 +
;gnome-hearts
 +
;gnome-mahjongg
 +
;gnome-mines
 +
;gnome-klotski
 +
;gnome-tetravex
  
[section version]
+
game system emulators:
  
python: 2.7
+
;gnomeboyadvance
 +
;gnome-mud
  
[section emerge]
+
=== Significant Known Issues (Workarounds Available) ===
 
+
 
+
[section snapshot]
+
 
+
type: live
+
compression: xz
+
 
+
[section snapshot/source]
+
 
+
type: git
+
branch: funtoo.org
+
# branch to have checked out for tarball:
+
branch/tar: origin/master
+
name: ports-2012
+
remote: git://github.com/funtoo/ports-2012.git
+
options: pull
+
 
+
[section metro]
+
 
+
options:
+
options/stage: cache/package
+
target: gentoo
+
 
+
[section baselayout]
+
 
+
services: sshd
+
 
+
[section multi]
+
 
+
snapshot: snapshot
+
 
+
[section files]
+
 
+
motd/trailer: [
+
 
+
>>> Send suggestions, improvements, bug reports relating to...
+
 
+
>>> This release:                  $[release/author]
+
>>> Funtoo Linux (general):        Funtoo Linux (http://www.funtoo.org)
+
>>> Gentoo Linux (general):        Gentoo Linux (http://www.gentoo.org)
+
]
+
 
+
[collect ../../multi-targets/$[multi/mode:zap]]
+
}}
+
  
= Building Gentoo stages =
+
[https://bugs.funtoo.org/browse/FL-1678 FL-1678]: Bluetooth interface gives wrong pairing key
  
Currently, Gentoo stages cannot be built in Metro. We have an open bug for this -- it is simply due to the fact that we focus on ensuring Funtoo Linux builds and building Gentoo is a lower priority. Historical note: Funtoo Linux originally started as a fork of Gentoo Linux so that metro could reliably build Gentoo stages.
+
[https://bugs.funtoo.org/browse/FL-1687 FL-1687]: Wallpaper corruption when resuming from suspend
  
[[Category:HOWTO]]
+
[[Category:Desktop]]
[[Category:Metro]]
+
[[Category:First Steps]]
__TOC__
+
[[Category:Official Documentation]]

Revision as of 17:45, February 22, 2015

What is GNOME?

"GNOME 3 is an easy and elegant way to use your computer. It is designed to put you in control and bring freedom to everybody. GNOME 3 is developed by the GNOME community, a diverse, international group of contributors that is supported by an independent, non-profit foundation." — GNOME

Prerequisites

From a Clean Install

Ensure that the X Window System is installed.

Preparing to emerge

To get your system ready to emerge gnome, first set your system flavor to desktop, and enable the gnome profile mix-in. To accomplish this, do the following:

# eselect profile set-flavor funtoo/1.0/linux-gnu/flavor/desktop
# eselect profile add funtoo/1.0/linux-gnu/mix-ins/gnome

Console: Set profile{{#subobject:|step=|stepCount=1|In recipe=setup,setup-light|+sep=,|action=runcmd|body=# ##i##eselect profile set-flavor funtoo/1.0/linux-gnu/flavor/desktop

  1. ##i##eselect profile add funtoo/1.0/linux-gnu/mix-ins/gnome}}

By enabling the gnome mix-in, various USE and other settings will be optimized to provide you with a pain-free GNOME installation experience.

Emerging

You are provided with two packages that will pull in this desktop environment:

  • gnome
Note

This is the "whole shabang" - pulls in a range of applications made for the gnome desktop environment including a few games, an archive manager, a system monitor, a web browser, a terminal, etc.

  • gnome-light
Note

As the name implies, this pulls in the base minimal you need to get a functioning GNOME Desktop Environment.

GNOME 3.14 from a clean install

gnome

To emerge gnome run the following command

#  emerge gnome

Console: Emerging GNOME

gnome-light

To emerge gnome-light run the following command

#  emerge gnome-light

Console: Emerging a minimal GNOME environment (alternative){{#subobject:|step=|stepCount=2|In recipe=setup-light|+sep=,|action=runcmd|body=# ##i## emerge gnome-light}}

Upgrading from GNOME 3.12

To update either gnome or gnome-light run the following command:

#  emerge -vauDN world

Subsystems

Bluetooth

For bluetooth support, ensure that:

  1. Bluetooth support is enabled in your kernel (using modules is fine).
  2. Your bluetooth hardware is turned on.
  3. Add the bluetooth startup script to the default runlevel, and start it.

This can be done as follows:

# rc-update add bluetooth default
# rc

Once this is done, you should now be able to navigate to Settings -> Bluetooth and turn bluetooth on. The icon next to devices should now animate and you should be able to discover and add devices such as keyboards.

Note

Additional kernel drivers may need to be enabled for certain input devices. For example, for the bluetooth Apple Magic Trackpad, the following option must be enabled in your kernel:

Under Device Drivers-->HID support-->HID bus support-->Special HID drivers:

<M> Apple Magic Mouse/Trackpad multi-touch support

Printing

To enable printing support, add cupsd to the default runlevel:

# rc-update add cupsd default
# rc

You should now be able to navigate to Settings -> Printers and add printers to your system, and print.

Scanning

To enable scanning support, add your user account to the lp group. This will allow your user to access the USB scanner.

Then, emerge xsane, and run it. It should be able to access your scanner.

Finishing Touches

X

Setting up xdm (GUI log-in)

Typically, you will want to use gdm, the GNOME display manager, to log in to GNOME. This will allow you to log in graphically, rather than using the text console.

To enable gdm, edit /etc/conf.d/xdm and set DISPLAYMANAGER to gdm instead of xdm. Then, perform the following steps to add xdm to the default runlevel, and have it start automatically from now on when your system starts:

Note

Funtoo's /etc/init.d/xdm initscript has been modified to start the requisite services dbus, openrc-settingsd and consolekit prior to starting gdm.

#  rc-update add xdm default

Console: Enable the GNOME display manager{{#subobject:|step=|stepCount=3|In recipe=setup|+sep=,|action=runcmd|body=# ##i## rc-update add xdm default}}

Then, if you want to start it now do:

# rc


But you should reboot to avoid having an open login terminal.

Setting up xinitrc (text log-in)

Adding the following to your ~/.xinitrc file is sufficient:

# Fix Missing Applications in Gnome
export XDG_MENU_PREFIX=gnome-

# Properly Launch the Desired X Session
exec ck-launch-session gnome-session

Additionaly, if you need support for different input sources, there is no longer a need to configure IBus or SCIM in your .xinitrc file as GNOME uses IBus natively. Simply configure it in the Control Center under Region & Language.

Automatically Starting Applications at Login

When using an old-fashioned .xinitrc, starting up applications when X starts is relatively easy. When using GDM, this can still be accomplished, by using the ~/.xprofile file. Here's my sample .xprofile to start xflux to dim the screen at night:

xflux -z 87107
Note

Remember to add a & at the end of any command that doesn't return to the shell prompt after running.

games

Gnome has several games that can be added on to your install. By default most games are not included in gnome's emerge.

Users wishing to play games need to be added to the games group:

# gpasswd -a $USER games


game list:

gnome-sudoku
gnome-mastermind
gnome-nibbles
gnome-robots
gnome-chess
gnome-hearts
gnome-mahjongg
gnome-mines
gnome-klotski
gnome-tetravex

game system emulators:

gnomeboyadvance
gnome-mud

Significant Known Issues (Workarounds Available)

FL-1678: Bluetooth interface gives wrong pairing key

FL-1687: Wallpaper corruption when resuming from suspend