Difference between pages "GNOME First Steps" and "Repository Configuration"

(Difference between pages)
 
(New repository layout)
 
Line 1: Line 1:
== What is GNOME? ==
+
{{Warning|This article is a work-in-progress referring to a future Portage version. It does not apply to the current Funtoo Portage version. Please do not update your configuration yet.}}
"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]
+
  
== Prerequisites ==
+
Starting with Portage-2.3.8, a switch to a new repository configuration framework is complete and users may want to update their configuration files. This document aims to describe the goals for the new framework and how to use it.
  
Before installing GNOME, ensure that the [[X Window System]] has been installed.
+
== Multiple repository layout ==
 +
One of the most important changes is the switch from the old ''overlay'' layout to a new cleaner ''repository'' system. The new layout is more flexible and more predictable. For example, repositories can now use resources (eclasses, for example) provided by other repositories.
  
{{fancywarning|1=
+
The old layout was based on the concept of one ''main tree'' and optionally a number of overlays. The main tree provided base system ebuilds, eclasses, profiles, while overlays mostly were able to provide their own ebuilds. The ebuild provided by overlays overrode the ebuilds in main tree to the extend of making it impossible to install the main tree version. Overlays could also provide eclasses for their own ebuilds and package.* entries that applied to all overlays and to the main tree. The Package Manager is responsible for updating the main tree, while overlays are managed externally.
Please note that Linux kernel 3.15.* may still have serious incompatibility with various graphics drivers. If you like to use <tt>gentoo-sources</tt> or <tt>vanilla-sources</tt>, please use a 3.14.* kernel. This is of particular importance if you plan to run GNOME, and want to use NVIDIA (commercial or nouveau) or ATI (ati-drivers) graphics drivers.}}
+
  
== Preparing to emerge ==
+
The new layout is based on the concept of one or more configurable repositories. Each repository can either be stand-alone or depend upon other repositories. The distribution provides a repository called ''funtoo'' (a drop-in replacement for Gentoo's ''gentoo'' repository). Users can install more repositories at they will, the repositories providing their own ebuilds, eclasses and profiles as necessary and/or using them from other repositories. Users can explicitly choose the repository they want to install packages from. The Package Manager can update all repositories.
  
To get your system ready to emerge gnome, it is recommended that you first set the gnome profile mix-in. To accomplish this, do the following:
+
== Portage configuration ==
<console>
+
=== New repository layout ===
##r### ##b## eselect profile list
+
The repository configuration should be stored in <code>/etc/portage/repos.conf</code>. It can be either a single file or a directory containing one or more ''.conf'' files.
##g##Currently available mix-ins profiles: 
+
  [11]  funtoo/1.0/linux-gnu/mix-ins/audio 
+
  [12]  funtoo/1.0/linux-gnu/mix-ins/console-extras 
+
  [13]  funtoo/1.0/linux-gnu/mix-ins/dvd 
+
  [14]  funtoo/1.0/linux-gnu/mix-ins/gnome 
+
  [15]  funtoo/1.0/linux-gnu/mix-ins/kde 
+
  [16]  funtoo/1.0/linux-gnu/mix-ins/mate 
+
  [17]  funtoo/1.0/linux-gnu/mix-ins/media 
+
  [18]  funtoo/1.0/linux-gnu/mix-ins/print 
+
  [19]  funtoo/1.0/linux-gnu/mix-ins/python3-only
+
  [20]  funtoo/1.0/linux-gnu/mix-ins/rhel5-compat
+
  [21]  funtoo/1.0/linux-gnu/mix-ins/server-db 
+
  [22]  funtoo/1.0/linux-gnu/mix-ins/server-mail
+
  [23]  funtoo/1.0/linux-gnu/mix-ins/server-web
+
  [24]  funtoo/1.0/linux-gnu/mix-ins/X
+
  [25]  funtoo/1.0/linux-gnu/mix-ins/xfce
+
  [26]  funtoo/1.0/linux-gnu/mix-ins/vmware-guest
+
  [27]  funtoo/1.0/linux-gnu/mix-ins/hardened
+
</console>
+
After seeing a list of available profiles, we want to add in the appropriate number for the gnome mix-in. To do this, run the following:
+
<console>
+
##r### ##b##eselect profile add 14
+
</console>
+
  
By enabling the gnome mix-in, various USE and other settings will be optimized to provide you with a pain-free GNOME installation experience.
+
The default configuration is installed as <code>/usr/share/portage/config/repos.conf</code>. This file is internal configuration file installed with portage ebuild and should '''not''' be modified. Instead, the configuration in <code>/etc/portage/repos.conf</code> can override the defaults specified there.
  
== Emerging ==
+
The configuration uses format similar to Windows .ini files. Each section heading (repository name in square brackets) signifies a single repository, followed by one or more key-value option pairs. For example, the following file copies default configuration for Funtoo repository:
  
You are provided with two packages that will pull in this desktop environment:  
+
{{file|name=/etc/portage/repos.conf/funtoo.conf|desc=Example configuration override for Funtoo repository|body=
 +
[funtoo]
 +
# moved to non-default location!
 +
location = /var/db/repos/funtoo
 +
sync-type = git
 +
sync-uri = git://github.com/funtoo/ports-2015.git
 +
auto-sync = yes
 +
}}
 +
Location variable is now what used to be a PORTDIR, when using old-fashioned <code>/etc/portage/make.conf</code>.  <code>/var/db/repos/funtoo</code> is a dummy location example. Default location in Funtoo is  set to <code>/usr/portage</code>. Users are free to choose a location of their suits. sync-type is a CVS tree used for portage tree, git is a default in Funtoo. sync-uri is what used to be a SYNC variable, when using old-fashioned configuration through <code>/etc/portage/make.conf</code>
 +
The most useful repository configuration options are listed below:
 +
;location: ''Obligatory.'' Specifies the directory where repository is/will be stored. If Portage knows how to sync the repository and the location does not exist, it will be created on next ''emerge --sync''. Otherwise, the directory must exist.
 +
;priority: Specifies the priority used for ordering ebuilds from different repositories. If two repositories provide an ebuild with matching versions, the repository with higher priority will be used.
 +
;auto-sync: Specifies whether ''emerge --sync'' should update the repository. Defaults to ''yes'' if ''sync-type'' is specified, ''no'' otherwise.
 +
;sync-depth: Specifies ''--depth'' for git clone. Used only on initial sync. Defaults to 1. Can be set to 0 to force full clone (not pass ''--depth'' at all).
 +
;sync-type: Specifies syncing/update method. Can be one of: ''cvs'', ''git'', ''rsync'', ''svn''.
 +
;sync-umask: Specifies the umask used when updating/syncing the repository.
 +
;sync-uri: Specifies remote URI from which the repository will be cloned/synced. Can use any syntax valid for a particular syncing method.
 +
;sync-user: Specifies the user[:group] used to update/sync the repository. If ''FEATURES=usersync'' is used, defaults to the credentials of directory owner.
  
* ''gnome''
+
[[Category:Portage]]
 
+
{{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.}}
+
 
+
* ''gnome-light''
+
 
+
{{fancynote|As the name implies, this pulls in the base minimal you need to get a functioning GNOME Desktop Environment.}}
+
 
+
=== GNOME 3.12 from a clean install ===
+
 
+
==== gnome ====
+
 
+
To emerge ''gnome'' run the following command
+
 
+
<console>
+
# ##i## emerge -va gnome
+
</console>
+
 
+
==== gnome-light ====
+
 
+
To emerge ''gnome-light'' run the following command
+
 
+
<console>
+
# ##i## emerge -va gnome-light
+
</console>
+
 
+
=== Upgrading from GNOME 3.6 ===
+
 
+
==== gnome ====
+
 
+
To emerge ''gnome'', remove nautilus-open-terminal if it is installed as it now bundled into gnome-terminal
+
 
+
<console>
+
# ##i## emerge -vaC nautilus-open-terminal
+
</console>
+
 
+
Then, run the following command
+
 
+
<console>
+
# ##i## emerge -vauDN world
+
</console>
+
 
+
==== gnome-light ====
+
 
+
To emerge ''gnome-light'' remove the following packages as there have been changes since 3.6 (you will have up reinstall any packages that have been renamed after gnome-light completes).
+
 
+
<console>
+
# ##i## emerge -vaC gnome-fallback gnome-panel gnome-screensaver metacity gnome-games gcalctool nautilus-open-terminal
+
</console>
+
 
+
Then, run the following command
+
 
+
<console>
+
# ##i## emerge -vauDN world
+
</console>
+
 
+
Finally, restore any applications that have been renamed (such as gcalctool => gnome-calculator)
+
 
+
<console>
+
# ##i## emerge -va gnome-calculator
+
</console>
+
 
+
== Subsystems ==
+
 
+
=== Bluetooth ===
+
 
+
For bluetooth support, ensure that:
+
 
+
# 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.
+
 
+
This can be done as follows:
+
 
+
<console>
+
# ##i##rc-update add bluetooth default
+
# ##i##rc
+
</console>
+
 
+
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.
+
 
+
=== Printing ===
+
 
+
To enable printing support, add <code>cupsd</code> to the default runlevel:
+
 
+
<console>
+
# ##i##rc-update add cupsd default
+
# ##i##rc
+
</console>
+
 
+
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 <code>lp</code> group. This will allow your user to access the USB scanner.
+
 
+
Then, <code>emerge xsane</code>, 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 <tt>gdm</tt>, 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 <tt>/etc/conf.d/xdm</tt> and set <tt>DISPLAYMANAGER</tt> to <tt>gdm</tt> instead of <tt>xdm</tt>. Then, perform the following steps to add <tt>xdm</tt> to the default runlevel, and have it start automatically from now on when your system starts:
+
 
+
<console>
+
# ##i##rc-update add xdm default
+
</console>
+
 
+
Then, if you want to start it now do
+
 
+
<console>
+
# ##i##rc
+
</console>
+
 
+
But you should reboot to avoid having an open login terminal
+
 
+
==== Setting up xinitrc (text log-in) ====
+
 
+
Adding the following to your <tt>~/.xinitrc</tt> file is sufficient:
+
 
+
<pre>
+
# Fix Missing Applications in Gnome
+
export XDG_MENU_PREFIX=gnome-
+
 
+
# Properly Launch the Desired X Session
+
exec ck-launch-session gnome-session
+
</pre>
+
 
+
Additionaly, if you need support for different input sources, there is no longer a need to configure ibus or scrim in your <tt>.xinitrc</tt> file as GNOME uses ibus natively. Simply configure it in the Control Center under Region & Langauge.
+
 
+
=== Verify the inode/directory MimeType Handler ===
+
 
+
In some odd instances, baobab might take priority over nautilus when handling the inode/directory MimeType. If this behavior is not desired, add the following to /home/~/.local/share/applications/mimeapps.list:
+
 
+
<pre>
+
[Added Associations]
+
inode/directory=nautilus.desktop;baobab.desktop;
+
</pre>
+
 
+
=== Automatically Starting Applications at Login ===
+
 
+
When using an old-fashioned <tt>.xinitrc</tt>, starting up applications when X starts is relatively easy. When using GDM, this can still be accomplished, by using the <tt>~/.xprofile</tt> file. Here's my sample <tt>.xprofile</tt> to start <tt>xflux</tt> to dim the screen at night:
+
 
+
<pre>
+
xflux -z 87107
+
</pre>
+
 
+
Remember to add a <tt>&</tt> at the end of any command that doesn't return to the shell prompt after running.
+
 
+
[[Category:Desktop Environments]]
+
[[Category:First Steps]]
+
[[Category:Official Documentation]]
+

Revision as of 13:52, February 14, 2015

Warning

This article is a work-in-progress referring to a future Portage version. It does not apply to the current Funtoo Portage version. Please do not update your configuration yet.

Starting with Portage-2.3.8, a switch to a new repository configuration framework is complete and users may want to update their configuration files. This document aims to describe the goals for the new framework and how to use it.

Multiple repository layout

One of the most important changes is the switch from the old overlay layout to a new cleaner repository system. The new layout is more flexible and more predictable. For example, repositories can now use resources (eclasses, for example) provided by other repositories.

The old layout was based on the concept of one main tree and optionally a number of overlays. The main tree provided base system ebuilds, eclasses, profiles, while overlays mostly were able to provide their own ebuilds. The ebuild provided by overlays overrode the ebuilds in main tree to the extend of making it impossible to install the main tree version. Overlays could also provide eclasses for their own ebuilds and package.* entries that applied to all overlays and to the main tree. The Package Manager is responsible for updating the main tree, while overlays are managed externally.

The new layout is based on the concept of one or more configurable repositories. Each repository can either be stand-alone or depend upon other repositories. The distribution provides a repository called funtoo (a drop-in replacement for Gentoo's gentoo repository). Users can install more repositories at they will, the repositories providing their own ebuilds, eclasses and profiles as necessary and/or using them from other repositories. Users can explicitly choose the repository they want to install packages from. The Package Manager can update all repositories.

Portage configuration

New repository layout

The repository configuration should be stored in /etc/portage/repos.conf. It can be either a single file or a directory containing one or more .conf files.

The default configuration is installed as /usr/share/portage/config/repos.conf. This file is internal configuration file installed with portage ebuild and should not be modified. Instead, the configuration in /etc/portage/repos.conf can override the defaults specified there.

The configuration uses format similar to Windows .ini files. Each section heading (repository name in square brackets) signifies a single repository, followed by one or more key-value option pairs. For example, the following file copies default configuration for Funtoo repository:

/etc/portage/repos.conf/funtoo.conf - Example configuration override for Funtoo repository
[funtoo]
# moved to non-default location!
location = /var/db/repos/funtoo
sync-type = git
sync-uri = git://github.com/funtoo/ports-2015.git
auto-sync = yes

Location variable is now what used to be a PORTDIR, when using old-fashioned /etc/portage/make.conf. /var/db/repos/funtoo is a dummy location example. Default location in Funtoo is set to /usr/portage. Users are free to choose a location of their suits. sync-type is a CVS tree used for portage tree, git is a default in Funtoo. sync-uri is what used to be a SYNC variable, when using old-fashioned configuration through /etc/portage/make.conf The most useful repository configuration options are listed below:

location
Obligatory. Specifies the directory where repository is/will be stored. If Portage knows how to sync the repository and the location does not exist, it will be created on next emerge --sync. Otherwise, the directory must exist.
priority
Specifies the priority used for ordering ebuilds from different repositories. If two repositories provide an ebuild with matching versions, the repository with higher priority will be used.
auto-sync
Specifies whether emerge --sync should update the repository. Defaults to yes if sync-type is specified, no otherwise.
sync-depth
Specifies --depth for git clone. Used only on initial sync. Defaults to 1. Can be set to 0 to force full clone (not pass --depth at all).
sync-type
Specifies syncing/update method. Can be one of: cvs, git, rsync, svn.
sync-umask
Specifies the umask used when updating/syncing the repository.
sync-uri
Specifies remote URI from which the repository will be cloned/synced. Can use any syntax valid for a particular syncing method.
sync-user
Specifies the user[:group] used to update/sync the repository. If FEATURES=usersync is used, defaults to the credentials of directory owner.