Difference between pages "Package:Xfce4-meta" and "Translations:Metro/122/en"

(Difference between pages)
(Removed the table of plugins at the bottom of the page, as that information is now contained by the XFCE Panel Plugins page and the Thunar Plugins page.)
 
(Importing a new version from external source)
 
Line 1: Line 1:
{{Ebuild
+
On my AMD Jaguar build server, on Feb 20, 2015, this lists all the builds that {{c|buildrepo}} has been configured to manage. The first number on each line is a '''failcount''', which is the number of consecutive times that the build has failed. A zero value indicates that everything's okay. The failcount is an important feature of the advanced repository management features. Here are a number of behaviors that are implemented based on failcount:
|Summary=Meta package for XFCE desktop
+
|CatPkg=xfce-base/xfce4-meta
+
|Maintainer=Oleg
+
}}
+
== About Xfce ==
+
<blockquote>
+
Xfce is a lightweight desktop environment for UNIX-like operating systems. It aims to be fast and low on system resources, while still being visually appealing and user friendly.
+
 
+
Xfce embodies the traditional UNIX philosophy of modularity and re-usability. It consists of a number of components that provide the full functionality one can expect of a modern desktop environment. They are packaged separately and you can pick among the available packages to create the optimal personal working environment.
+
 
+
Another priority of Xfce is adhereance to standards, specifically those defined at [http://freedesktop.org/ freedesktop.org]. [[http://www.xfce.org/about/ About XFCE]]
+
</blockquote>
+
== Installation ==
+
 
+
Before emerging Xfce you need to:
+
 
+
Check that you have enabled the USE flags necessary for a XFCE desktop environment. Set your profile to "xfce" via [[Funtoo_Linux_First_Steps#Changing_profile|mix-ins]], as follows:
+
{{console|body=
+
###i## epro mix-ins +xfce
+
}}
+
Then, verify that you have the [[Funtoo_Linux_First_Steps#X.Org|X.Org Server]] configured properly. If X.Org is installed on your system, you are now ready to install Xfce. Install the meta-package, which pulls in all of the components you need for a minimal Xfce installation:
+
 
+
{{console|body=
+
###i## emerge xfce4-meta
+
}}
+
== Running Xfce ==
+
 
+
There are several different ways to start Xfce:
+
 
+
* Editing the {{c|.xinitrc}} file in your user's home directory and using {{c|startx}} from a text console.
+
* Using a display manager (e.g. SLiM, GDM, and KDM).
+
* Configuring your shell profile to automatically start Xfce upon a successful login.
+
=== .xinitrc ===
+
 
+
The most common way to start the environment is to configure {{c|~/.xinitrc}} to launch an Xfce session. The proper way to launch Xfce from the terminal is by using {{c|startxfce4}} combined with {{c|ck-launch-session}}.
+
 
+
{{console|body=
+
$##i## echo "exec startxfce4 --with-ck-launch" > ~/.xinitrc
+
}}
+
Note that {{c|--with-ck-launch}} (from ConsoleKit) is required by Xfce for important tasks such as shutting down, suspending, and automatically mounting removable storage media. Some applications will not work properly without it. Also, configuring the GTK+ theme and other forms of theming through {{Package|Xfce4-settings}} do not often work without the {{c|--with-ck-launch}} command line option. Because we are launching XFCE with a consolekit command line option, we need to add ConsoleKit to the {{c|default}} runlevel, executing the following command as root:
+
 
+
{{console|body=
+
###i## rc-update add consolekit default
+
###i## rc
+
}}
+
Finally, to start the graphical environment, run {{c|startx}} from a login shell:
+
 
+
{{console|body=
+
$##i## startx
+
}}
+
After running this command, you should be greeted by your shiny new XFCE desktop. For more information about configuring XFCE and some of the default applications that come with it, consider looking at [[Package:xfce4-meta#XFCE configuration and XFCE applications|XFCE configuration and XFCE applications]].
+
== Display Manager ==
+
 
+
A display manager is a program that manages sessions and acts as a login screen. Here's a short list of a few of the display managers available from the Funtoo repositories:
+
* XDM ({{c|x11-apps/xdm}}): X.Org's standard display manager.
+
* LightDM ({{c|x11-misc/lightdm}}): A lightweight, but highly configurable display manager.
+
* SLiM ({{c|x11-misc/slim}}): Simple Login Manager -- a lightweight display manager. Not very configurable.
+
 
+
 
+
Any of these would make a fine choice. After you've chosen which display manager to use, install it:
+
 
+
{{console|body=###i## emerge <display manager of choice>}}
+
All that's left to do now is to add the name of the display manager to {{c|/etc/conf.d/xdm}}, add the {{c|xdm}} service and the {{c|dbus}} service to the {{c|default}} runlevel, and start the services:
+
 
+
{{file|name=/etc/conf.d/xdm|desc=|body=
+
DISPLAYMANAGER="<display manager name>"
+
}}
+
 
+
{{console|body=
+
###i## rc-update add xdm default
+
###i## rc-update add dbus default
+
###i## rc
+
}}
+
==Power Group==
+
If you wish to be able to shutdown/reboot/suspend/hibernate using xfce4-logout-session then you will need to add yourself or the user to the power group by:
+
 
+
{{console|body=
+
###i## gpasswd -a <username> power
+
}}
+
If the group does not exist then execute the following and try again:
+
 
+
{{console|body=
+
###i## groupadd power}}
+
== XFCE configuration and XFCE applications ==
+
For more information on configuring XFCE and the default applications provided by XFCE, such as {{c|xfce4-terminal}}, consider following some of the below listed links:
+
* [[Package:Xfce4-settings|GUI settings configuration for XFCE]]
+
* [[Package:Xfce4-terminal|The default terminal emulator for XFCE]]
+
* [[Package:Whiskermenu|An alternate menu for the XFCE panel]]
+
* [[XFCE Panel Plugins|A list of the various plugins available for {{c|xfce4-panel}}]]
+
* [[Thunar Plugins|A list of the plugins available for the Thunar file manager]]
+
 
+
[[Category:Desktop]]
+
[[Category:First Steps]]
+
[[Category:Official Documentation]]
+
{{EbuildFooter}}
+

Latest revision as of 17:31, July 12, 2015

On my AMD Jaguar build server, on Feb 20, 2015, this lists all the builds that buildrepo has been configured to manage. The first number on each line is a failcount, which is the number of consecutive times that the build has failed. A zero value indicates that everything's okay. The failcount is an important feature of the advanced repository management features. Here are a number of behaviors that are implemented based on failcount: