Difference between revisions of "Funtoo Profiles"

From Funtoo
Jump to navigation Jump to search
m (→‎For Developers: - removed outdated info)
m (add kde-plasma-5 to the list of mix-ins)
(36 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{#widget:AddThis}}
{{#widget:AddThis}}
{{PageNeedsUpdates}}
<languages/>
== What is a profile? ==
<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.
== Profile Types == <!--T:1-->


In Gentoo and Funtoo Linux, profiles are used to define base system settings, and have historically had a lot of untapped potential. In Funtoo Linux, I 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.
<!--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:


== What It Is ==
<!--T:3-->
{{TableStart}}
{{2ColHead|Sub-Profile Type|Description}}
{{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.}}
{{2Col|{{c|build}}|Defines whether your system is a {{c|current}}, {{c|stable}} or {{c|experimental}} 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.}}
{{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 setting that is compatible with your CPU.}}
{{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.}}
{{2Col|{{c|mix-ins}}|Defines various optional settings that you may be interested in enabling.}}
{{TableEnd}}


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.
<!--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.}}


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.
=== Using epro === <!--T:5-->


In Funtoo Linux, multiple profiles can be enabled at the same time. These include:
<!--T:6-->
{{c|epro show}} will display the current profile settings on your system:
</translate>
{{console|body=
# ##i## epro show


* '''arch''' - one arch profile is enabled, at build time, and is not changed. This defines CPU architecture-specific settings.
=== ##g##Enabled Profiles##!g##: ===
* '''build''' - one build profile is enabled, at build time, and is generally not changed. It defines the type of build, such as 'current' or 'stable', and associated settings.
* '''flavor''' - one flavor is enabled per system, and can be changed by the user. This defines the general use of the system, such as 'minimal', 'core', 'workstation' or 'desktop'
* '''mix-in''' - zero or more mix-ins can be enabled that enable settings specific to a particular subset of features, such as 'gnome', 'kde', 'media', 'mate', 'X', 'hardened'


{{note|1=
        arch: ##c## x86-64bit
See [[Flavors and Mix-ins]] for a complete list of all flavors and mix-ins available in Funtoo Linux, along with descriptions of what each one does.}}
      build: ##c## current
    subarch: ##c## intel64-haswell
      flavor: ##c## desktop
    mix-ins: ##c## gnome


=== Origins and Benefits ===


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:
=== ##g##All inherited flavors from desktop flavor##!g##: ===


* Fewer settings in <code>/etc/make.conf</code>. <code>CHOST</code> and <code>ARCH</code> no longer set in <code>/etc/make.conf</code>.
                    ##c##workstation##!c## (from desktop flavor)
* Separation of concerns -- arch, build, and flavor-related settings are organized together.
                            ##c##core##!c## (from workstation flavor)
* User flexibility - any number of mix-ins can be enabled to tweak masks or USE settings as needed.
                        ##c##minimal##!c## (from core flavor)
 
=== ##g##All inherited mix-ins from desktop flavor##!g##: ===
 
                              ##c##X##!c## (from workstation flavor)
                          ##c##audio##!c## (from workstation flavor)
                            ##c##dvd##!c## (from workstation flavor)
                          ##c##media##!c## (from workstation flavor)
      ##c##mediadevice-audio-consumer##!c## (from media mix-in)
                ##c##mediadevice-base##!c## (from mediadevice-audio-consumer mix-in)
      ##c##mediadevice-video-consumer##!c## (from media mix-in)
                ##c##mediadevice-base##!c## (from mediadevice-video-consumer mix-in)
        ##c##mediaformat-audio-common##!c## (from media mix-in)
          ##c##mediaformat-gfx-common##!c## (from media mix-in)
        ##c##mediaformat-video-common##!c## (from media mix-in)
                  ##c##console-extras##!c## (from workstation 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.


{{note|See [[Custom Profiles]] for information on how to extend the profile system.}}
==== Usage Examples ==== <!--T:8-->


=== Using ego / epro ===
<!--T:9-->
epro is a new personality tool designed to eventually replace eselect profile.  If your desired subarch is not listed with "eselect profile list", try using "epro list".
{{TableStart}}
{{2Col|Add the mix-ins {{c|gnome}} and {{c|kde}}|{{console|body=# ##i## epro mix-ins +gnome +kde}}}}
{{2Col|Remove a mix-in, for example {{c|gnome}}|{{console|body=# ##i## epro mix-ins -gnome}}}}
{{2Col|Change the profile arch to x86-64bit|{{console|body=# ##i## epro arch x86-64bit}}}}
{{2Col|Change the subarch to {{c|generic_64}}|{{console|body=# ##i## epro subarch generic_64}}}}
{{2Col|Change the system flavor|{{console|body=# ##i## epro flavor desktop}}}}
{{2Col|Get JSON output of profile settings|{{console|body=# ##i## epro show-json}}}}
{{2Col|Get current sub-profile setting in text form|{{console|body=# ##i## epro get [profiletype]}}}}
{{TableEnd}}


For more information, see this news: [http://www.funtoo.org/News:Better_Experiences:_Ego_and_Vim News: Better Experiences: Ego and Vim]
== Flavors == <!--T:10-->


And the ego wiki page itself: [[Package:Ego]]
<!--T:11-->
{{SectionNeedsUpdates}}
A system can have only one flavor profile enabled at a time. The following flavors are available:


=== Using epro ===
<!--T:12-->
The preferred method of adding and removing profiles is to use [[epro]]. This will ensure that profiles are added correctly and in the proper order. The order is imperative for things to work right.
{{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}}


Type the following to view a list of available options for '''epro''':
== Mix-ins == <!--T:13-->
For a start, let's see what the default configuration has to offer. Get an overview using the '''list''' command:
<console>
###i## epro list
=== arch: ===


    arm-32bit, (pure64*), x86-32bit, x86-64bit
<!--T:14-->
A system can have any number of mix-ins enabled at a time. The following mix-ins are available:


=== subarch: ===
<!--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}}


    amd64-bulldozer-pure64, amd64-jaguar-pure64, amd64-k10-pure64
=== Media Device Mix-ins === <!--T:16-->
    amd64-k8+sse3-pure64, amd64-k8-pure64, amd64-piledriver-pure64
    amd64-steamroller-pure64, atom_64-pure64, btver1_64-pure64
    core-avx-i-pure64, core2_64-pure64, corei7-pure64, generic_64-pure64*
    intel64-broadwell-pure64, intel64-haswell-pure64, intel64-ivybridge-pure64
    intel64-nehalem-pure64, intel64-sandybridge-pure64, intel64-silvermont-pure64
    intel64-westmere-pure64, native_64-pure64, nocona-pure64, opteron_64-pure64
    xen-pentium4+sse3_64-pure64


=== build: ===
<!--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:


    (current*), experimental, stable
<!--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}}


=== flavor: ===
=== Media Format Mix-ins === <!--T:19-->


    core, desktop*, hardened, minimal, server, workstation
<!--T:20-->
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:


=== mix-ins: ===
<!--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}}


    X, audio, cinnamon, console-extras, dvd, gnome, hardened, kde
=== How to Use Media Mix-Ins === <!--T:22-->
    lxde, lxqt, mate, media, media-pro, mediadevice-audio-consumer
    mediadevice-audio-pro, mediadevice-base, mediadevice-video-consumer
    mediadevice-video-pro, mediaformat-audio-common, mediaformat-audio-extra
    mediaformat-gfx-common, mediaformat-gfx-extra, mediaformat-video-common
    mediaformat-video-extra, no-emul-linux-x86, no-systemd, print
    python3-only, vmware-guest, xfce*
</console>


As in several other Funtoo utilities, a star ('''*''') on the right indicates an active item (your case may differ from the example above).
<!--T:23-->
Now, let's head over and add some mix-ins. To add, say, the mix-ins '''gnome''' and '''kde''' we'd have to enter:
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 +kde
* {{c|mediadevice-audio-consumer}}
</console>
* {{c|mediadevice-video-consumer}}
If we want to remove a mix-in, for example '''gnome''', simply enter:
* {{c|mediaformat-audio-common}}
* {{c|mediaformat-gfx-common}}
* {{c|mediaformat-video-common}}


<console>
<!--T:25-->
###i## epro mix-ins -gnome
In addition, there is a new {{c|media-pro}} mix-in which needs to be enabled manually, which pulls in the following mix-ins:
</console>


{{fancywarning|Please, do not add anything manually into <code>parent</code> file. This may result in profile breakage.}}
<!--T:26-->
* {{c|mediadevice-audio-pro}}
* {{c|mediadevice-video-pro}}


<!--T:27-->
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.


The contents of <code>/etc/portage/make.profile/parent</code> for a basic setup might look like this:
=== How Profile Settings are Stored === <!--T:28-->


<!--T:29-->
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:
</translate>
{{file|name=/etc/portage/make.profile/parent|body=
{{file|name=/etc/portage/make.profile/parent|body=
gentoo:funtoo/1.0/linux-gnu/arch/x86-64bit
gentoo:funtoo/1.0/linux-gnu/arch/x86-64bit
Line 102: Line 178:
gentoo:funtoo/1.0/linux-gnu/flavor/core
gentoo:funtoo/1.0/linux-gnu/flavor/core
}}
}}
 
<translate>
A more rounded setup for a desktop might look like this:
<!--T:30-->
 
Profile settings for a desktop might look like this:
</translate>
{{file|name=/etc/portage/make.profile/parent|body=
{{file|name=/etc/portage/make.profile/parent|body=
gentoo:funtoo/1.0/linux-gnu/arch/x86-64bit
gentoo:funtoo/1.0/linux-gnu/arch/x86-64bit
Line 112: Line 189:
gentoo:funtoo/1.0/linux-gnu/mix-ins/media
gentoo:funtoo/1.0/linux-gnu/mix-ins/media
}}
}}
<translate>
== History and Origins == <!--T:31-->


== Related ==
<!--T:32-->
* [[Flavors and Mix-ins]]
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>.
* 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.
<!--T:34-->
{{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:Labs]]
[[Category:HOWTO]]
[[Category:HOWTO]]
[[Category:Official Documentation]]
[[Category:Official Documentation]]

Revision as of 00:17, December 10, 2015

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 or experimental 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.

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 kde
root #  epro mix-ins +gnome +kde
Remove a mix-in, for example gnome
root #  epro mix-ins -gnome
Change the profile arch to x86-64bit
root #  epro arch x86-64bit
Change the subarch to generic_64
root #  epro subarch generic_64
Change the system flavor
root #  epro flavor desktop
Get JSON output of profile settings
root #  epro show-json
Get current sub-profile setting in text form
root #  epro get [profiletype]

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.

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.