注意：

The Funtoo Linux project has transitioned to "Hobby Mode" and this wiki is now read-only.

Difference between revisions of "Funtoo Profiles"

From Funtoo
Jump to navigation Jump to search
(cleanups)
(Marked this version for translation)
 
(41 intermediate revisions by 8 users not shown)
Line 1: Line 1:
{{#widget:AddThis}}
{{#widget:AddThis}}
__TOC__
<languages/>
 
<translate>This page covers the Funtoo Linux profile system -- how it works, what profiles are available, and how to use [[#Using epro|{{c|epro}}]] to set and change profile settings.
This page covers the Funtoo Linux profile system -- how it works, what profiles are available, and how to use [[#epro|{{c|epro}}]] to set and change profile settings.
   
   
== What is a profile? ==
== Profile Types == <!--T:1-->
 
In Gentoo and Funtoo Linux, profiles are used to define base system settings for Portage, and have historically had a lot of untapped potential. In Funtoo Linux, Daniel Robbins wanted to take advantage of some of this potential to allow Funtoo Linux users to easily tailor their system for various types of roles. Enter the new Funtoo profile system.
 
== Profile Types ==
 
Historically, users have had to add a ton of settings to <code>/etc/[[make.conf]]</code> to customize their Gentoo or Funtoo Linux system, which made setup of the operating system more difficult than it should be. In Gentoo Linux, it is possible to only define one ''system profile''. Think of a system profile as the default settings that Portage uses for building everything on your system. Funtoo Linux uses multiple profiles per system. The following profile types are available in Funtoo Linux:
 
{{TableStart}}
{{2Col|{{c|arch}}|One arch profile is enabled, at build time, and is not changed. This defines CPU architecture-specific settings.}}
{{2Col|{{c|subarch}}|One subarch profile is typically enabled at build time, and defines the CPU optimizations in use.}}
{{2Col|{{c|build}}|One build profile is enabled, at build time, and is generally not changed. It defines the type of build, such as {{c|current}} or {{c|stable}}, and associated settings.}}
{{2Col|{{c|flavor}}|One flavor is enabled per system, and can be changed by the user. This defines the general use of the system, such as {{c|minimal}}, {{c|core}}, {{c|workstation}} or {{c|desktop}}}}
{{2Col|{{c|mix-ins}}|Zero or more mix-ins can be enabled that enable settings specific to a particular subset of features, such as {{c|gnome}}, {{c|kde}}, {{c|media}}, {{c|mate}}, {{c|X}}, {{c|hardened}}.}}
{{TableEnd}}


== Flavors ==
<!--T:2-->
 
Historically, users have had to add a large number of settings to [[Make.conf|{{c|/etc/make.conf}}]] to customize their Gentoo or Funtoo Linux system, which made setup of the operating system more difficult than it should be. In Gentoo Linux, it is possible to only define one ''system profile''. Think of a system profile as the default settings that Portage uses for building everything on your system. Rather than a single profile, Funtoo Linux uses multiple sub-profiles, and moves many types of settings that are normally stored in {{c|/etc/make.conf}} into the profile system. The following profile types are available in Funtoo Linux:
A system can have only one flavor profile enabled at a time. The following flavors are available:


<!--T:3-->
{{TableStart}}
{{TableStart}}
<tr><td>{{c|minimal}}</td><td>This flavor defines the most minimal possible flavor. It currently only contains defaults for all Funtoo Linux flavors.</td></tr>
{{2ColHead|Sub-Profile Type|Description}}
<tr><td>{{c|core}}</td><td>The core flavor is the minimal flavor plus reasonable USE options, and is used for stage3 builds.</td></tr>
{{2Col|{{c|arch}}|Typically {{c|x86-32bit}} or {{c|x86-64bit}}, this defines the processor type and support of your system. This is defined when your stage was built and should not be changed.}}
<tr><td>{{c|server}}</td><td>The server flavor is intended for servers but at this time just tracks core.</td></tr>
{{2Col|{{c|build}}|Defines whether your system is a {{c|current}}, {{c|stable}}, {{c|experimental}} or {{c|next}} build. {{c|current}} systems will have newer packages unmasked than {{c|stable}} systems. This is defined when your stage is built and is typically not changed.}}
<tr><td>{{c|workstation}}</td><td>The workstation flavor is a minimal desktop system. It includes the core flavor plus these mix-ins: {{c|X}}, {{c|audio}}, {{c|dvd}}, {{c|media}} and {{c|console-extras}}.</td></tr>
{{2Col|{{c|subarch}}|Defines CPU optimizations for your system. The subarch is set at the time the stage3 is built, but can be changed later to better settings if necessary. Be sure to pick a [[Subarches|setting that is compatible with your CPU]].}}
<tr><td>{{c|desktop}}</td><td>The desktop flavor is a full-featured desktop system, minus desktop environment (add KDE, GNOME or XFCE as a mix-in.) It includes the {{c|workstation}} flavor plus {{c|printing}} support.</td></tr>
{{2Col|{{c|flavor}}|Defines the general type of system, such as {{c|server}} or {{c|desktop}}, and will set default USE flags appropriate for your needs.}}
{{TableEnd}}
{{2Col|{{c|mix-ins}}|Defines various optional settings that you may be interested in enabling.}}
 
== Mix-ins ==
 
A system can have any number of mix-ins enabled at a time. The following mix-ins are available:
 
{{TableStart}}
{{2Col|{{c|audio}}|Enables core audio-related settings, currently related to ALSA.}}
{{2Col|{{c|console-extras}}|Enables things that are nice to have for console-only systems. Currently enabling gpm in USE.}}
{{2Col|{{c|dvd}}|USE settings related to optical drives -- CDR/DVD-ROM/RW use.}}
{{2Col|{{c|gnome}}|USE and package.use settings required to merge GNOME. Designed to be used with {{c|desktop}} or {{c|workstation}} flavor.}}
{{2Col|{{c|hardened}}|Enables hardened support.}}
{{2Col|{{c|kde}}|USE and package.use settings required to merge KDE. Designed to be used with {{c|desktop}} or {{c|workstation}} flavor.}}
{{2Col|{{c|media}}|USE settings related to audio/video media encoding. Can be for desktops or servers.}}
{{2Col|{{c|print}}|Enables printing capability.}}
{{2Col|{{c|vmware-guest}}|Settings related to using Funtoo Linux as a VMWare virtual machine guest.}}
{{2Col|{{c|X}}|Settings related to the X Window System and hardware support.}}
{{2Col|{{c|xfce}}|USE settings required for merging XFCE.}}
{{TableEnd}}
{{TableEnd}}


=== Setting Profiles ===
<!--T:4-->
{{Note|Flavors can (and often do) inherit settings from other flavors and mix-ins. Mix-ins can also inherit settings from other mix-ins. For example, {{c|X}} is inherited by {{c|gnome}}. The {{c|epro}} tool will show both as being enabled so there are no surprises.}}


Funtoo Linux stores its profile settings in the {{f|/etc/portage/make.profile/parent}} file. Typically, users don't need to modify this file, instead using {{c|ego}} and {{c|epro}} to make changes, but it can be handy to take a look at what the contents of the file look like. A simple server might have profile settings as follows:
=== The Purpose === <!--T:35-->


{{file|name=/etc/portage/make.profile/parent|body=
<!--T:36-->
gentoo:funtoo/1.0/linux-gnu/arch/x86-64bit
The purpose of this new system is to:
gentoo:funtoo/1.0/linux-gnu/build/current
gentoo:funtoo/1.0/linux-gnu/flavor/core
}}


Profile settings for a desktop might look like this:
<!--T:37-->
# '''Help developers to organize and curate optimal settings for the community.''' We use these settings, such as our {{c|gnome}} mix-in, to build official GNOME stages. So we want them to work, and work well.
# Allow our users to use the {{c|epro}} tool (also known as its long form: {{c|ego profile}} to manage {{c|USE}} settings in bulk. '''We want our mix-ins to be useful for enabling a logical set of {{c|USE}} flags by name''', such as {{c|mediaformat-audio-extra}} rather than listing a long list of {{c|USE}} flags.


{{file|name=/etc/portage/make.profile/parent|body=
<!--T:38-->
gentoo:funtoo/1.0/linux-gnu/arch/x86-64bit
Really, we consider the selection and maintenance of optimal {{c|USE}} settings to be a ''community task'', rather than an ''individual task''. This is a fundamental cultural difference of Funtoo as compared to Gentoo.
gentoo:funtoo/1.0/linux-gnu/build/current
gentoo:funtoo/1.0/linux-gnu/flavor/desktop
gentoo:funtoo/1.0/linux-gnu/mix-ins/dvd
gentoo:funtoo/1.0/linux-gnu/mix-ins/media
}}


=== Using epro ===
<!--T:39-->
See the [[Wolf Pack Philosophy]] for more information on these cultural differences which have a practical impact on how we do our work.


Remember that profiles can often be inherited. For example, the <code>desktop</code> flavor inherits the <code>workstation</code> flavor settings, which in turn inherits the <code>X</code> and <code>audio</code> mix-ins. You can view this by using {{c|epro}}:
=== Using epro === <!--T:5-->


<!--T:6-->
{{c|epro show}} will display the current profile settings on your system:
</translate>
{{console|body=
{{console|body=
# ##i## epro show
# ##i##epro show


=== ##g##Enabled Profiles##!g##: ===
=== ##g##Enabled Profiles##!g##: ===
Line 88: Line 55:
=== ##g##All inherited flavors from desktop flavor##!g##: ===
=== ##g##All inherited flavors from desktop flavor##!g##: ===


                     ##c##workstation (from desktop flavor)
                     ##c##workstation##!c## (from desktop flavor)
                             ##c##core (from workstation flavor)
                             ##c##core##!c## (from workstation flavor)
                         ##c##minimal (from core flavor)
                         ##c##minimal##!c## (from core flavor)


=== ##g##All inherited mix-ins from desktop flavor##!g##: ===
=== ##g##All inherited mix-ins from desktop flavor##!g##: ===
Line 108: Line 75:
                           ##c##print##!c## (from desktop flavor)
                           ##c##print##!c## (from desktop flavor)
}}
}}
<translate><!--T:7-->
To view all available sub-profile settings, use {{c|epro list}}:
{{console|body=# ##i##epro list}}
Enabled profiles will be highlighted in cyan. Directly enabled profiles will be in bold and have an asterisk {{c|*}} appended. Sub-profiles enabled via inheritance will be highlighted.
==== Usage Examples ==== <!--T:8-->
<!--T:9-->
{{TableStart}}
{{2Col|Add the mix-ins {{c|gnome}} and {{c|kde}}|{{c|epro mix-ins +gnome +kde}}}}
{{2Col|Remove a mix-in, for example {{c|gnome}}|{{c|epro mix-ins -gnome}}}}
{{2Col|Change the profile arch to x86-64bit|{{c|epro arch x86-64bit}}}}
{{2Col|Change the subarch to {{c|generic_64}}|{{c|epro subarch generic_64}}}}
{{2Col|Change the system flavor|{{c|epro flavor desktop}}}}
{{2Col|Get JSON output of profile settings|{{c|epro show-json}}}}
{{2Col|Get current sub-profile setting in text form|{{c|epro get [profiletype]}}}}
{{TableEnd}}
=== Wrapping Up === <!--T:40-->
After you set your desired profile, sync and update.
{{console|body=# ##i## ego sync}}
{{console|body=# ##i## emerge -auDN @world}}
== Flavors == <!--T:10-->
<!--T:11-->
A system can have only one flavor profile enabled at a time. The following flavors are available:
<!--T:12-->
{{TableStart}}
{{2ColHead|Flavor|Description}}
<tr><td>{{c|minimal}}</td><td>This contains the bare minimum settings for all Funtoo Linux flavors.</td></tr>
<tr><td>{{c|core}}</td><td>The core flavor includes the minimal flavor, plus reasonable settings, and is used for the [[Funtoo_Linux_Installation#Installing_the_Stage_3_tarball|official stage3 downloads]].</td></tr>
<tr><td>{{c|server}}</td><td>In the future, the server flavor will include the core flavor, plus specific settings designed for servers. At the moment, it is equivalent to the core flavor.</td></tr>
<tr><td>{{c|workstation}}</td><td>The workstation flavor is a minimal desktop system. It includes the core flavor, plus these mix-ins: {{c|X}}, {{c|audio}}, {{c|dvd}}, {{c|media}} and {{c|console-extras}}.</td></tr>
<tr><td>{{c|desktop}}</td><td>The desktop flavor includes the common settings for any full-featured desktop system. It includes the {{c|workstation}} flavor plus {{c|printing}} support. The user is expected to further customize their system with a desktop environment of choice, such as KDE, GNOME, or XFCE, possibly by using a mix-in.</td></tr>
{{TableEnd}}
== Mix-ins == <!--T:13-->
<!--T:14-->
A system can have any number of mix-ins enabled at a time. The following mix-ins are available:
<!--T:15-->
{{TableStart}}
{{2ColHead|Mix-in|Description}}
{{2Col|{{c|audio}}|Enables core audio-related settings, currently related to ALSA.}}
{{2Col|{{c|console-extras}}|Enables things that are nice to have for console-only systems. Currently enabling gpm in USE.}}
{{2Col|{{c|dvd}}|USE settings related to optical drives -- CDR/DVD-ROM/RW use.}}
{{2Col|{{c|gnome}}|USE and package.use settings required to merge GNOME. Designed to be used with {{c|desktop}} or {{c|workstation}} flavor.}}
{{2Col|{{c|hardened}}|Enables hardened support.}}
{{2Col|{{c|kde}}|USE and package.use settings required to merge KDE Plasma 4. Designed to be used with {{c|desktop}} or {{c|workstation}} flavor.}}
{{2Col|{{c|kde-plasma-5}}|USE and package.use settings required to merge KDE Plasma 5. Designed to be used with {{c|desktop}} or {{c|workstation}} flavor.}}
{{2Col|{{c|media}}|USE settings related to audio/video media encoding. Can be for desktops or servers.}}
{{2Col|{{c|print}}|Enables printing capability.}}
{{2Col|{{c|vmware-guest}}|Settings related to using Funtoo Linux as a VMware virtual machine guest.}}
{{2Col|{{c|X}}|Settings related to the X Window System and hardware support.}}
{{2Col|{{c|xfce}}|USE settings required for merging XFCE.}}
{{TableEnd}}
<!--T:41-->
{{SectionNeedsUpdates}}
=== Media Device Mix-ins === <!--T:16-->
<!--T:17-->
Media device mix-ins have been created to support media devices, including external and portable devices, and associated low-level hardware support and hardware-focused codecs. Media devices have been categorized into audio and video categories, and consumer and professional categories. "Consumer" devices are those devices that regular desktop users might typically use, while "professional" devices are those that professionals, hobbyists or enthusiasts would typically use. Here are the new mix-ins for media devices:
<!--T:18-->
{{TableStart}}
{{2ColHead|Media Device Mix-in|Description}}
<tr><td>{{c|mediadevice-base}}</td><td>Common, universally-supported media devices, like IEEE-1394 (Firewire), CDDA, CDIO. Other mediadevice mix-ins have this as a parent.</td></tr>
<tr><td>{{c|mediadevice-audio-consumer}}</td><td>Consumer audio devices, such as personal portable media players (iOS, iPod, etc.)</td></tr>
<tr><td>{{c|mediadevice-audio-pro}}</td><td>Pro audio support, such as JACK.</td></tr>
<tr><td>{{c|mediadevice-video-consumer}}</td><td>Consumer video support, such as DVD, Blu Ray, V4L</td></tr>
<tr><td>{{c|mediadevice-video-pro}}</td><td>Pro video support, such as dv, dc1394.</td></tr>
{{TableEnd}}


To view available profiles:
=== Media Format Mix-ins === <!--T:19-->
{{console|body=
# ##i## epro list
}}


Enabled profiles will be highlighted in cyan. Directly enabled profiles will be in bold and have an asterisk {{c|*}} appended.
<!--T:20-->
Highlighted items are enabled via inheritance.
Media format mix-ins have been created to support media formats for reading, writing, encoding and decoding images, audio and video. They have been organized into a "common" collection, for popular formats, and an "extra" collection, which is intended to include "everything else". Let's look at the new mix-ins:


To add the mix-ins {{c|gnome}} and {{c|kde}}, we'd enter:
<!--T:21-->
{{TableStart}}
{{2ColHead|Media Format Mix-in|Description}}
<tr><td>{{c|mediaformat-video-common}}</td><td>Common (ie. popular) video formats.</td></tr>
<tr><td>{{c|mediaformat-video-extra}}</td><td>More esoteric video formats.</td></tr>
<tr><td>{{c|mediaformat-audio-common}}</td><td>Common (ie. popular) audio formats.</td></tr>
<tr><td>{{c|mediaformat-audio-extra}}</td><td>More esoteric audio formats.</td></tr>
<tr><td>{{c|mediaformat-gfx-common}}</td><td>Common (ie. popular) graphics formats.</td></tr>
<tr><td>{{c|mediaformat-gfx-extra}}</td><td>More esoteric graphics formats.</td></tr>
{{TableEnd}}


<console>
=== How to Use Media Mix-Ins === <!--T:22-->
###i## epro mix-ins +gnome +kde
</console>


If we want to remove a mix-in, for example {{c|gnome}}, simply enter:
<!--T:23-->
Our existing {{c|media}} mix-in still exists, and is still pulled in by the {{c|desktop}} and {{c|workstation}} flavors automatically. It now includes the following parent mix-ins:


<console>
<!--T:24-->
###i## epro mix-ins -gnome
* {{c|mediadevice-audio-consumer}}
</console>
* {{c|mediadevice-video-consumer}}
* {{c|mediaformat-audio-common}}
* {{c|mediaformat-gfx-common}}
* {{c|mediaformat-video-common}}


To change the profile arch to x86-64:
<!--T:25-->
{{console|body=###i## epro arch x86-64bit}}
In addition, there is a new {{c|media-pro}} mix-in which needs to be enabled manually, which pulls in the following mix-ins:


To change the build to current:
<!--T:26-->
{{console|body=###i## epro build current}}
* {{c|mediadevice-audio-pro}}
* {{c|mediadevice-video-pro}}


To change the subarch to generic_64:
<!--T:27-->
{{console|body=###i## epro subarch generic_64}}
So typically, you would enable the {{c|desktop}} or {{c|workstation}} flavor, and if you need professional hardware support, you'd also enable the {{c|media-pro}} mix-in. If you needed any additional media formats support, you could enable one or more of the {{c|mediaformat-*-extra}} mix-ins to add the formats you needed. Of course, it's possible to enable only the specific mix-ins you need, and also complement these mix-ins with specific USE variable settings you might require.


To change the profile flavor:
=== How Profile Settings are Stored === <!--T:28-->
{{console|body=
# ##i## epro flavor desktop
}}


To get a JSON output of your profile info:
<!--T:29-->
{{console|body=
Funtoo Linux stores its profile settings in the {{f|/etc/portage/make.profile/parent}} file. Typically, users don't need to modify this file, instead using {{c|ego}} and {{c|epro}} to make changes, but it can be handy to take a look at what the contents of the file look like. A simple server might have profile settings as follows:
# ##i## epro show-json
</translate>
{{file|name=/etc/portage/make.profile/parent|body=
gentoo:funtoo/1.0/linux-gnu/arch/x86-64bit
gentoo:funtoo/1.0/linux-gnu/build/current
gentoo:funtoo/1.0/linux-gnu/flavor/core
}}
}}
 
<translate>
To get the current value of a given profile:
<!--T:30-->
{{console|body=
Profile settings for a desktop might look like this:
# ##i## epro get build|flavor|arch|subarch|mix-ins
</translate>
{{file|name=/etc/portage/make.profile/parent|body=
gentoo:funtoo/1.0/linux-gnu/arch/x86-64bit
gentoo:funtoo/1.0/linux-gnu/build/current
gentoo:funtoo/1.0/linux-gnu/flavor/desktop
gentoo:funtoo/1.0/linux-gnu/mix-ins/dvd
gentoo:funtoo/1.0/linux-gnu/mix-ins/media
}}
}}
<translate>


== History and Origins ==
== History and Origins == <!--T:31-->


This new system is really a completion of the original cascading profile design that was designed by Daniel Robbins and implemented by Seemant Kulleen as part of Portage. Funtoo Profiles designed to leverage the existing cascading profile system and provide something much more useable and maintainable for users and developers alike. Here are some of its benefits:
<!--T:32-->
This new system is really a completion of the original cascading profile design that was co-designed by Daniel Robbins and Seemant Kulleen and implemented by Seemant Kulleen as part of Portage. Funtoo Profiles designed to leverage the existing cascading profile system and provide something much more useable and maintainable for users and developers alike. Here are some of its benefits:


<!--T:33-->
* Fewer settings in <code>/etc/make.conf</code>. <code>CHOST</code> and <code>ARCH</code> no longer set in <code>/etc/make.conf</code>.
* Fewer settings in <code>/etc/make.conf</code>. <code>CHOST</code> and <code>ARCH</code> no longer set in <code>/etc/make.conf</code>.
* Separation of concerns -- arch, build, and flavor-related settings are organized together.
* Separation of concerns -- arch, build, and flavor-related settings are organized together.
* User flexibility - any number of mix-ins can be enabled to tweak masks or USE settings as needed.
* User flexibility - any number of mix-ins can be enabled to tweak masks or USE settings as needed.


<!--T:34-->
{{note|See [[Custom Profiles]] for information on how to extend the profile system.}}
{{note|See [[Custom Profiles]] for information on how to extend the profile system.}}
 
</translate>
[[Category:Funtoo features]]
[[Category:Funtoo features]]
[[Category:Portage]]
[[Category:Portage]]
[[Category:HOWTO]]
[[Category:HOWTO]]
[[Category:Official Documentation]]
[[Category:Official Documentation{{#translation:}}]]

Latest revision as of 19:39, January 26, 2023

Other languages:
English • ‎Türkçe • ‎español • ‎português do Brasil • ‎slovenčina • ‎русский • ‎中文（中国大陆）‎ • ‎日本語

This page covers the Funtoo Linux profile system -- how it works, what profiles are available, and how to use epro to set and change profile settings.

Profile Types

Historically, users have had to add a large number of settings to /etc/make.conf to customize their Gentoo or Funtoo Linux system, which made setup of the operating system more difficult than it should be. In Gentoo Linux, it is possible to only define one system profile. Think of a system profile as the default settings that Portage uses for building everything on your system. Rather than a single profile, Funtoo Linux uses multiple sub-profiles, and moves many types of settings that are normally stored in /etc/make.conf into the profile system. The following profile types are available in Funtoo Linux:

Sub-Profile TypeDescription
archTypically x86-32bit or x86-64bit, this defines the processor type and support of your system. This is defined when your stage was built and should not be changed.
buildDefines whether your system is a current, stable, experimental or next build. current systems will have newer packages unmasked than stable systems. This is defined when your stage is built and is typically not changed.
subarchDefines CPU optimizations for your system. The subarch is set at the time the stage3 is built, but can be changed later to better settings if necessary. Be sure to pick a setting that is compatible with your CPU.
flavorDefines the general type of system, such as server or desktop, and will set default USE flags appropriate for your needs.
mix-insDefines various optional settings that you may be interested in enabling.
   Note

Flavors can (and often do) inherit settings from other flavors and mix-ins. Mix-ins can also inherit settings from other mix-ins. For example, X is inherited by gnome. The epro tool will show both as being enabled so there are no surprises.

The Purpose

The purpose of this new system is to:

  1. Help developers to organize and curate optimal settings for the community. We use these settings, such as our gnome mix-in, to build official GNOME stages. So we want them to work, and work well.
  2. Allow our users to use the epro tool (also known as its long form: ego profile to manage USE settings in bulk. We want our mix-ins to be useful for enabling a logical set of USE flags by name, such as mediaformat-audio-extra rather than listing a long list of USE flags.

Really, we consider the selection and maintenance of optimal USE settings to be a community task, rather than an individual task. This is a fundamental cultural difference of Funtoo as compared to Gentoo.

See the Wolf Pack Philosophy for more information on these cultural differences which have a practical impact on how we do our work.

Using epro

epro show will display the current profile settings on your system: 

root # epro show

=== Enabled Profiles: ===

        arch:  x86-64bit
       build:  current
     subarch:  intel64-haswell
      flavor:  desktop
     mix-ins:  gnome


=== All inherited flavors from desktop flavor: ===

                     workstation (from desktop flavor)
                            core (from workstation flavor)
                         minimal (from core flavor)

=== All inherited mix-ins from desktop flavor: ===

                               X (from workstation flavor)
                           audio (from workstation flavor)
                             dvd (from workstation flavor)
                           media (from workstation flavor)
      mediadevice-audio-consumer (from media mix-in)
                mediadevice-base (from mediadevice-audio-consumer mix-in)
      mediadevice-video-consumer (from media mix-in)
                mediadevice-base (from mediadevice-video-consumer mix-in)
        mediaformat-audio-common (from media mix-in)
          mediaformat-gfx-common (from media mix-in)
        mediaformat-video-common (from media mix-in)
                  console-extras (from workstation flavor)
                           print (from desktop flavor)

To view all available sub-profile settings, use epro list: 

root # epro list

Enabled profiles will be highlighted in cyan. Directly enabled profiles will be in bold and have an asterisk * appended. Sub-profiles enabled via inheritance will be highlighted.

Usage Examples

Add the mix-ins gnome and kdeepro mix-ins +gnome +kde
Remove a mix-in, for example gnomeepro mix-ins -gnome
Change the profile arch to x86-64bitepro arch x86-64bit
Change the subarch to generic_64epro subarch generic_64
Change the system flavorepro flavor desktop
Get JSON output of profile settingsepro show-json
Get current sub-profile setting in text formepro get [profiletype]

Wrapping Up

After you set your desired profile, sync and update. 

root #  ego sync
root #  emerge -auDN @world

Flavors

A system can have only one flavor profile enabled at a time. The following flavors are available:

FlavorDescription
minimalThis contains the bare minimum settings for all Funtoo Linux flavors.
coreThe core flavor includes the minimal flavor, plus reasonable settings, and is used for the official stage3 downloads.
serverIn the future, the server flavor will include the core flavor, plus specific settings designed for servers. At the moment, it is equivalent to the core flavor.
workstationThe workstation flavor is a minimal desktop system. It includes the core flavor, plus these mix-ins: X, audio, dvd, media and console-extras.
desktopThe desktop flavor includes the common settings for any full-featured desktop system. It includes the workstation flavor plus printing support. The user is expected to further customize their system with a desktop environment of choice, such as KDE, GNOME, or XFCE, possibly by using a mix-in.

Mix-ins

A system can have any number of mix-ins enabled at a time. The following mix-ins are available:

Mix-inDescription
audioEnables core audio-related settings, currently related to ALSA.
console-extrasEnables things that are nice to have for console-only systems. Currently enabling gpm in USE.
dvdUSE settings related to optical drives -- CDR/DVD-ROM/RW use.
gnomeUSE and package.use settings required to merge GNOME. Designed to be used with desktop or workstation flavor.
hardenedEnables hardened support.
kdeUSE and package.use settings required to merge KDE Plasma 4. Designed to be used with desktop or workstation flavor.
kde-plasma-5USE and package.use settings required to merge KDE Plasma 5. Designed to be used with desktop or workstation flavor.
mediaUSE settings related to audio/video media encoding. Can be for desktops or servers.
printEnables printing capability.
vmware-guestSettings related to using Funtoo Linux as a VMware virtual machine guest.
XSettings related to the X Window System and hardware support.
xfceUSE settings required for merging XFCE.


   Important

This section is in need of updates.


Media Device Mix-ins

Media device mix-ins have been created to support media devices, including external and portable devices, and associated low-level hardware support and hardware-focused codecs. Media devices have been categorized into audio and video categories, and consumer and professional categories. "Consumer" devices are those devices that regular desktop users might typically use, while "professional" devices are those that professionals, hobbyists or enthusiasts would typically use. Here are the new mix-ins for media devices:

Media Device Mix-inDescription
mediadevice-baseCommon, universally-supported media devices, like IEEE-1394 (Firewire), CDDA, CDIO. Other mediadevice mix-ins have this as a parent.
mediadevice-audio-consumerConsumer audio devices, such as personal portable media players (iOS, iPod, etc.)
mediadevice-audio-proPro audio support, such as JACK.
mediadevice-video-consumerConsumer video support, such as DVD, Blu Ray, V4L
mediadevice-video-proPro video support, such as dv, dc1394.

Media Format Mix-ins

Media format mix-ins have been created to support media formats for reading, writing, encoding and decoding images, audio and video. They have been organized into a "common" collection, for popular formats, and an "extra" collection, which is intended to include "everything else". Let's look at the new mix-ins:

Media Format Mix-inDescription
mediaformat-video-commonCommon (ie. popular) video formats.
mediaformat-video-extraMore esoteric video formats.
mediaformat-audio-commonCommon (ie. popular) audio formats.
mediaformat-audio-extraMore esoteric audio formats.
mediaformat-gfx-commonCommon (ie. popular) graphics formats.
mediaformat-gfx-extraMore esoteric graphics formats.

How to Use Media Mix-Ins

Our existing media mix-in still exists, and is still pulled in by the desktop and workstation flavors automatically. It now includes the following parent mix-ins:

  • mediadevice-audio-consumer
  • mediadevice-video-consumer
  • mediaformat-audio-common
  • mediaformat-gfx-common
  • mediaformat-video-common

In addition, there is a new media-pro mix-in which needs to be enabled manually, which pulls in the following mix-ins:

  • mediadevice-audio-pro
  • mediadevice-video-pro

So typically, you would enable the desktop or workstation flavor, and if you need professional hardware support, you'd also enable the media-pro mix-in. If you needed any additional media formats support, you could enable one or more of the mediaformat-*-extra mix-ins to add the formats you needed. Of course, it's possible to enable only the specific mix-ins you need, and also complement these mix-ins with specific USE variable settings you might require.

How Profile Settings are Stored

Funtoo Linux stores its profile settings in the /etc/portage/make.profile/parent file. Typically, users don't need to modify this file, instead using ego and epro to make changes, but it can be handy to take a look at what the contents of the file look like. A simple server might have profile settings as follows:

   /etc/portage/make.profile/parent 
gentoo:funtoo/1.0/linux-gnu/arch/x86-64bit
gentoo:funtoo/1.0/linux-gnu/build/current
gentoo:funtoo/1.0/linux-gnu/flavor/core

Profile settings for a desktop might look like this:

   /etc/portage/make.profile/parent 
gentoo:funtoo/1.0/linux-gnu/arch/x86-64bit
gentoo:funtoo/1.0/linux-gnu/build/current
gentoo:funtoo/1.0/linux-gnu/flavor/desktop
gentoo:funtoo/1.0/linux-gnu/mix-ins/dvd
gentoo:funtoo/1.0/linux-gnu/mix-ins/media

History and Origins

This new system is really a completion of the original cascading profile design that was co-designed by Daniel Robbins and Seemant Kulleen and implemented by Seemant Kulleen as part of Portage. Funtoo Profiles designed to leverage the existing cascading profile system and provide something much more useable and maintainable for users and developers alike. Here are some of its benefits:

  • Fewer settings in /etc/make.conf. CHOST and ARCH no longer set in /etc/make.conf.
  • Separation of concerns -- arch, build, and flavor-related settings are organized together.
  • User flexibility - any number of mix-ins can be enabled to tweak masks or USE settings as needed.
   Note

See Custom Profiles for information on how to extend the profile system.

Retrieved from "https://www.funtoo.org/index.php?title=Funtoo_Profiles&oldid=42988"