Difference between pages "Funtoo:About/pt-br" and "Funtoo Profiles/ru"

(Difference between pages)
(Posso Usá-lo (Can I Use It)?)
 
(Created page with "=== Использование медиа-дополнений ===")
 
Line 1: Line 1:
= Visão do Projeto =
+
{{#widget:AddThis}}
 +
<languages/>
 +
== Типы профилей ==
  
Daniel Robbins originalmente escreveu a [[ Gentoo Linux Philosophy|Filosofia Gentoo Linux]], e nisso definiu o conceito de uma ferramenta ideal assim sendo algo que "simplesmente funciona", não fica no caminho do usuário, e responde a vontade do usuário ao invés de forçar o usuário a trabalhar de um jeito particular.
+
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. Funtoo Linux uses multiple sub-profiles per system. The following profile types are available in Funtoo Linux:
  
Funtoo Linux é um projeto de pessoas que concordam filosofia da ferramenta ideal, e que são ''apaixonados'' pelo nosso desejo de melhorar a tecnologia de ser tão próximo desse ideial quanto possível. O foco de nossos esforços é o melhoramento contínuo da distribuição Gentoo Linux.  
+
{{TableStart}}
 +
{{2ColHead|Sub-Profile|Description}}
 +
{{2Col|{{c|arch}}|This defines CPU-specific settings. Only one arch profile is enabled at install time, and cannot be changed.}}
 +
{{2Col|{{c|subarch}}|This further refines the CPU-specific settings. One subarch profile is typically enabled at install time.}}
 +
{{2Col|{{c|build}}|This defines the type of stability, such as {{c|current}} or {{c|stable}}, and its associated settings. One build profile is enabled, at install time, and is generally not changed.}}
 +
{{2Col|{{c|flavor}}|This defines the intended use of Funtoo, such as {{c|minimal}}, {{c|core}}, {{c|workstation}} or {{c|desktop}}. One flavor is enabled, and can be changed by the user.}}
 +
{{2Col|{{c|mix-ins}}|These can be enabled by the user, based on the features the user wants, such as {{c|gnome}}, {{c|kde}}, {{c|media}}, {{c|mate}}, {{c|X}}, and {{c|hardened}}.}}
 +
{{TableEnd}}
  
O foco do desenvolvimento do Funtoo Linux é atualmente direcionado ao sistema central (core system), significando qualquer coisa em um stage3, portage, core languages, kernels, aplicações de servidor, e em cima do X11 e gerenciadores de janelas simples, e incluindo ambientes desktop como o GNOME e o KDE.
+
{{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.}}
  
== Foco, Foco, Foco ==
+
=== Использование epro ===
  
Desenvolvedores deveriam utilizar esses princípios gerais para determinar em quais prioridades focar primeiro. -Essas areas abaixo estão listadas em ordem de prioridade, então o próximo parágrafo é a principal prioridade (top priority), seguido pela próxima prioridade, etc. Só por que algo é prioridade mais baixa não significa que é "menos importante" - somente significa tratar as coisas de prioridades mais altas (higher-priority) antes.
+
{{c|epro show}} отображает текущие настройки профилей в вашей системе:
 +
{{console|body=
 +
# ##i## epro show
  
=== Ele controe (Does it Build)? ===
+
=== ##g##Enabled Profiles##!g##: ===
  
* '''Ele constrói confiavelmente?'''
+
        arch: ##c## x86-64bit
 +
      build: ##c## current
 +
    subarch: ##c## intel64-haswell
 +
      flavor: ##c## desktop
 +
    mix-ins: ##c## gnome
  
O primeiro teste - o software constrói a partir do código fonte corretamente? Isso não se trata somente de emergir ebuilds no seu sistema -- O builds do stage funciona sem problemas utilizando o Metro? Se não, isso precisa ser corrigido primeiro. O Funtoo Linux continuamente constrói lançamentos de do sistema operacional atualizados, e essa devem ser construídas confiavelmente em todos os momentos. O fóco aqui é para builds 100% corretos e eficientes utilizando o Metro, e depois emergindo aplicações iniciais em um sistema Funtoo Linux.
 
  
=== Ele executa (Does It Run)? ===
+
=== ##g##All inherited flavors from desktop flavor##!g##: ===
  
* '''Ele executa bem?'''
+
                    ##c##workstation (from desktop flavor)
 +
                            ##c##core (from workstation flavor)
 +
                        ##c##minimal (from core flavor)
  
OK, ele constrói. Ele executa corretamente? Ele funciona? Isso é bem vago, então vamos colocar algumas especificações aqui. Quando instalar o Funtoo Linux a partir do stage3, tudo funciona? Quais complicações ou falhas foram  encontradas na instalação inicial? Essas devem ser corrigidas, ou soluções devem ser colocadas no lugar, e correções a longo prazo devem ser trabalhadas para melhorar a experiência do usuário. Lembre-se de que o foco do Funtoo Linux é no sistema central - Essa é a coisa que você toca quando você instala o Funtoo Linux pela primeira vez. Você deve reinstalar o Funtoo Linux regularmente para verificar por quaisquer questões e priorizar as questões de instalação do usuário e a experiência inicial do usuário.
+
=== ##g##All inherited mix-ins from desktop flavor##!g##: ===
  
=== Posso Usá-lo (Can I Use It)? ===
+
                              ##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)
 +
}}
 +
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.
  
* '''Facilmente (Easily)?'''
+
==== Примеры использования ====
* '''Para Trabalho de Verdade (For Real Work)?'''
+
  
OK, ele constrói, e executa. Mas eu posso realizar tarefas de verdade com a ferramenta? Qual é a facilidade ou dificuldade  de realizar essas tarefas? A tecnologia (e documentação) devem ser projetadas oferecer suporte ao usuário na questão de realizar estas tarefas, ao invés de forçar o usuário a saltar por arcos obter algo configurado corretamente. As coisas devem ser automatizadas o tanto o quanto possível sem assumir controle distante do usuário. Razoável, padrões seguros que são adequados para a cargas produtivas devem ser utilizadas por todas as aplicações. As coisas devem emergir sem bloqueadores ou ausência de recursos que devem ser habilitadas manualmente pelo usuário. E uma implicância - se o emerge parar de dizer ao usuário que eles devem definir uma variável USE para que continue, isso é algo que deve ser corrigido de um jeito ou de outro. Então, quando tudo é dito e feito, ele deve funcionar.
+
{{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}}
  
=== Is It Documented? ===
+
== Конфигурации ==
  
* '''For free software projects, documentation is key.'''
+
В системе можно одновременно задействовать только один профиль конфигурации. Доступны следующие варианты:
  
If software builds, runs and works, others still may not be able to use it until proper documentation is available. Upstream documentation isn't always complete or easy to understand, so often additional user documentation is required. If manual steps are required, they should be documented clearly and correctly. The documentation option of choice is the Funtoo wiki as well as man pages.
+
{{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}}
  
For source code, verbose comments should be used. You may be working on the code now, but someone else might be working on it six months from now. Developers are expected to write clear comments that are sufficiently non-technical and provide the necessary context to allow less experienced developers to understand critical parts of code, and ideally '''all''' parts of the code. Please see [[Coding Standards]].
+
== Дополнения ==
  
=== Is It Well-Designed? ===
+
Одновременно в системе может быть задействовано любое количество дополнений. Доступные следующие варианты дополнений:
  
* '''Optimized?'''
+
{{TableStart}}
* '''Maintainable?'''
+
{{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. 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}}
  
It builds and runs, and I can use it to perform real work. But is the system well-designed? Does it work reliably? Are all available patches and fixes in place to ensure a reliable computing experience? Is Funtoo Linux providing the best technology possible to users? And is this technology easy to maintain? Remember, all things being equal, less code is better than more code because it is easier to maintain. Are there verbose comments in code where necessary?
+
=== Дополнения для мультимедийных устройств ===
  
=== Are We Getting Better? ===
+
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:
  
OK, we're doing all of the above steps. Here is the next test - are we getting better? Is the quality, security, usability and maintainability of the distribution improving over time, or is it going up, and then going down, and we're not really making any forward progress? The ultimate goal at the end of the day is to make forward progress in the quality of the distribution. This requires better automation, better tools, better processes, and investment in research and development and new ways of doing things. It also requires the right attitude. If we are doing a lot of work and the overall quality of the distribution is not improving, then our efforts are not making a long-term difference, even though they may be addressing immediate bugs and issues. We must ensure that our efforts are worthwhile, and they are making a positive long-term difference in the quality of the distribution.
+
{{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}}
  
=== What is The Real Problem? ===
+
=== Дополнения для медиа-форматов ===
  
Building on this theme - when a bug is encountered, what is the ''real'' problem, or ''root cause''? Strategic thinking as well as in-depth troubleshooting is required to identify the root cause of a problem. Should we just fix root causes? No, this is impractical, because doing this takes a lot of time. Instead, workarounds are often used to quickly restore quality to acceptable levels. However, just implementing workarounds is dangerous, because bugs tend to multiply while the underlying issue goes unresolved. The proper solution is to implement workarounds but to not lose focus on the need to address the underlying issues, or root causes, of the problem. In fact, much of the focus of Funtoo Linux is on this last step - aggressively fixing a bunch of immediate issues so we can start to address the deeper problems once and for all...
+
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:
  
=== Architecture ===
+
{{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}}
  
...and addressing root causes of problems often requires a significant change in software architecture. Funtoo Linux is a project that is not afraid of making significant, even aggressive, architectural changes in order to fix problems. This is what our users expect us to do, and ''as long as these changes are properly tested, managed, planned, automated and communicated to users'', they will not get upset. As stated in the previous paragraph, the Funtoo Linux project is zealous about addressing these core architectural issues -- but we need to get a handle on the more fundamental challenges first. Once workarounds are in place, we'll take a stab at some core system change that will pay dividends well into the future.
+
=== Использование медиа-дополнений ===
  
== Examples ==
+
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:
  
Below, you will find examples of existing efforts that have aligned with these goals. This section will give you a feel for how real projects can be started that align with the Funtoo Linux vision defined above.
+
* {{c|mediadevice-audio-consumer}}
 +
* {{c|mediadevice-video-consumer}}
 +
* {{c|mediaformat-audio-common}}
 +
* {{c|mediaformat-gfx-common}}
 +
* {{c|mediaformat-video-common}}
  
=== Boot-Update ===
+
In addition, there is a new {{c|media-pro}} mix-in which needs to be enabled manually, which pulls in the following mix-ins:
  
[[Boot-Update]] was designed by Daniel Robbins to provide a more elegant way to configure boot loaders under Funtoo Linux. This project was prioritized for several reasons. For one, it had to do with the initial installation experience (see [[#Does it Run?]]) Also, lack of GRUB2 support, as well as GPT/GUID support, was identified as a critical weakness in current Gentoo Linux functionality (see [[#Is it Well-Designed?]]) Because of this, a new unified configurator was written which uses <tt>/etc/boot.conf</tt> as the global boot loader configuration file. This represented a change in boot loader architecture (see [[#Architecture]]) under Funtoo Linux, in order to improve usability and flexibilty over existing solutions, and to attempt to reduce or eliminate a class of problems related to boot loader configuration, which is especially troublesome with GRUB2.
+
* {{c|mediadevice-audio-pro}}
 +
* {{c|mediadevice-video-pro}}
  
=== Metro ===
+
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.
  
[[Metro]] was designed by Daniel Robbins and is used to address the "[[#Does It Build?]]" question. The existing solution, catalyst, was difficult to maintain (see [[#Is It Well-Designed?]]), so Metro was developed to provide a new mechanism for building OS releases.
+
=== How Profile Settings are Stored ===
  
=== Forked Ebuilds ===
+
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:
 +
{{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
 +
}}
 +
Profile settings for a desktop might look like this:
 +
{{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
 +
}}
 +
== History and Origins ==
  
Not all improvements involve large software development efforts. In fact, the majority of fixes involve relatively small fixes to ebuilds. These fixes are often made to fix a Metro build failure (see [[#Does it Build?]]) or address some quality issue (see [[#Is It Well-Designed?]]). The <tt>www-servers/nginx</tt> ebuild was improved to provide better default settings for production systems, with corresponding changes made to <tt>sys-libs/pam</tt> to allow this to work. <tt>dev-lang/python</tt> contains fixes to ensure that Metro builds complete properly and a valid <tt>/usr/bin/python</tt> symlink always exists.
+
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:
  
=== OpenVZ ===
+
* 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.
  
OpenVZ support is a specific priority of Funtoo Linux. Funtoo Linux maintains a patched <tt>sys-cluster/vzctl</tt> with various patches to fix a variety of problems. In addition, <tt>openvz-rhel6-stable</tt> and <tt>openvz-rhel5-stable</tt> ebuilds have been created to ease installation of production-quality OpenVZ kernels (see [[#Can I Use It?]]) In addition, [[OpenVZ]] documentation exists on the wiki (see [[#Can I Use It?]])
+
{{note|See [[Custom Profiles]] for information on how to extend the profile system.}}
 
+
[[Category:Funtoo features]]
[[Category:QA]]
+
[[Category:Portage]]
 +
[[Category:HOWTO]]
 +
[[Category:Official Documentation]]

Revision as of 17:25, July 27, 2015

Other languages:
English • ‎português do Brasil • ‎русский

Типы профилей

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. Funtoo Linux uses multiple sub-profiles per system. The following profile types are available in Funtoo Linux:

Sub-ProfileDescription
archThis defines CPU-specific settings. Only one arch profile is enabled at install time, and cannot be changed.
subarchThis further refines the CPU-specific settings. One subarch profile is typically enabled at install time.
buildThis defines the type of stability, such as current or stable, and its associated settings. One build profile is enabled, at install time, and is generally not changed.
flavorThis defines the intended use of Funtoo, such as minimal, core, workstation or desktop. One flavor is enabled, and can be changed by the user.
mix-insThese can be enabled by the user, based on the features the user wants, such as gnome, kde, media, mate, X, and hardened.
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.

Использование epro

epro show отображает текущие настройки профилей в вашей системе:

#  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:

#  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.

Примеры использования

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

Конфигурации

В системе можно одновременно задействовать только один профиль конфигурации. Доступны следующие варианты:

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

Использование медиа-дополнений

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.