Difference between revisions of "Funtoo 1.0 Profile"

From Funtoo Linux
Jump to: navigation, search
(Touched on the need to be aware of the PORTDIR, DISTDIR and PKGDIR location changes.)
m (→‎Related read)
(31 intermediate revisions by 15 users not shown)
Line 2: Line 2:
 
[[Category:Labs]]
 
[[Category:Labs]]
 
[[Category:HOWTO]]
 
[[Category:HOWTO]]
−
 
 
= What It Is =
 
= What It Is =
  
−
The main idea behind The Funtoo 1.0 Profile is to do away with the current necessity of jumping-through-hoops in order to configure your system. It aims for a [[Unified Configuration]] by collating these files and directories:
+
The main idea behind the Funtoo 1.0 Profile is to do away with the current monolithic "one size fits all" approach. Instead of setting one massive profile and then overriding whatever you don't want, the Funtoo 1.0 Profile uses a new multi profile approach which allows way more flexibility and customization. Instead of having to remove what you don't want, now you'll be able to add in just the parts that you do want and leave out the rest.
−
 
+
−
<pre>
+
−
/etc/make.conf
+
−
/etc/make.profile (symlink)
+
−
/etc/portage/
+
−
</pre>
+
−
 
+
−
Into a single "system profile":
+
−
 
+
−
<pre>
+
−
/etc/portage/
+
−
</pre>
+
  
 
= How It Works =
 
= How It Works =
  
−
Please check [[Funtoo 1.0 Profile: Internals]].
+
Please check [[Funtoo 1.0 Profile: Internals]](Coming Soon).
  
 
= What It Looks Like =
 
= What It Looks Like =
−
 
+
Here's a what a list of profiles looks like:
−
A finished /etc/portage directory contains the following files and directories:
+
−
 
+
 
<pre>
 
<pre>
−
bin/                    [...]
+
starmine portage # eselect profile list
−
eapi                    Define the EAPI version to maintain Gentoo Linux compatibility.
+
Currently available arch profiles:
−
make.defaults          What was previously known as the /etc/make.conf file.
+
  [1]   funtoo/1.0/linux-gnu/arch/x86-32bit
−
overlays                Define overlays.
+
  [2]  funtoo/1.0/linux-gnu/arch/x86-64bit
−
package.env/           Define environment files (one package per atom).
+
Currently available build profiles:
−
package.keywords/       Define accepted architecture/Funtoo branch keywords for individual packages.
+
  [3]  funtoo/1.0/linux-gnu/build/stable
−
package.license/       Define accepted licenses for individual packages.
+
  [4]  funtoo/1.0/linux-gnu/build/current
−
package.mask/           Define masks for individual packages.
+
  [5]  funtoo/1.0/linux-gnu/build/experimental
−
package.properties/     [...]
+
Currently available flavor profiles:
−
package.unmask/         Define unmasks for individual packages.
+
  [6]  funtoo/1.0/linux-gnu/flavor/minimal
−
package.use/           Define use flags for individual packages.
+
  [7]  funtoo/1.0/linux-gnu/flavor/core
−
parent                  Define the profile sub-sets you wish to use.
+
  [8]   funtoo/1.0/linux-gnu/flavor/desktop
−
portdir                Define the path to your portage directory.
+
  [9]  funtoo/1.0/linux-gnu/flavor/workstation
−
postsync.d/             [...]
+
Currently available mix-ins profiles:
−
profile/               [...]
+
  [10]  funtoo/1.0/linux-gnu/mix-ins/audio
−
savedconfig/           Storage for configuration files that need to be included while building a special package.
+
  [11]  funtoo/1.0/linux-gnu/mix-ins/console-extras
 +
  [12]  funtoo/1.0/linux-gnu/mix-ins/dvd
 +
  [13]  funtoo/1.0/linux-gnu/mix-ins/gnome
 +
  [14]  funtoo/1.0/linux-gnu/mix-ins/kde
 +
  [15]  funtoo/1.0/linux-gnu/mix-ins/media
 +
  [16] funtoo/1.0/linux-gnu/mix-ins/print
 +
  [17]  funtoo/1.0/linux-gnu/mix-ins/python3-only
 +
  [18]  funtoo/1.0/linux-gnu/mix-ins/rhel5-compat
 +
  [19]  funtoo/1.0/linux-gnu/mix-ins/server-db
 +
  [20]  funtoo/1.0/linux-gnu/mix-ins/server-mail
 +
  [21] funtoo/1.0/linux-gnu/mix-ins/server-web
 +
  [22]  funtoo/1.0/linux-gnu/mix-ins/X
 +
  [23]  funtoo/1.0/linux-gnu/mix-ins/xfce
 
</pre>
 
</pre>
−
 
+
As you can see, there are multiple types of profiles to choose from.
−
Note that the new structure of is similar to the old one except for a few changes and that the file/directory duality of package.* remains.
+
Let's move on to how to start using it.
−
 
+
−
= How To Use It =
+
−
 
+
−
== Prepare the System ==
+
−
 
+
−
This is only applicable if you are using the "portage.git" or "portage-mini-2010.git" portage trees.
+
−
 
+
−
=== Switch to the Latest Portage Tree ===
+
−
 
+
−
1. First, emerge --sync and emerge -u portage to ensure you have the latest (unmasked)
+
−
version of Portage running.
+
−
 
+
−
2. Then, back up your old Portage tree:
+
−
 
+
−
<pre>
+
−
cd /usr
+
−
mv portage portage.old
+
−
</pre>
+
−
 
+
−
3. Next, edit /etc/make.conf and remove any hard-coded SYNC= variable from
+
−
the file. The latest Portage has the correct default. You probably have a
+
−
SYNC= line even if you didn't add it yourself. You need to ensure it's
+
−
removed.
+
−
 
+
−
4. Now, grab the new 2011 tree by running "emerge --sync".
+
−
 
+
−
5. "cat /usr/portage/.git/config" and ensure that the "url" line ends in
+
−
"portage-mini-2011.git" - this confirms you now have the latest 2011 tree.
+
−
 
+
−
6. Make sure your new tree is working fine, emerge a few things, etc.
+
−
 
+
−
7. Once you have confirmed that your new Portage tree is working, you can
+
−
now "rm -rf /usr/portage.old" to save some disk space.
+
  
 
== Switch to the Funtoo 1.0 Profile ==
 
== Switch to the Funtoo 1.0 Profile ==
 +
=== Define the profile sub-sets you will use ===
  
−
{{fancywarning|The Funtoo 1.0 Profile is still in development and should not be used in production environments!}}
+
So far in Funtoo we have used the exact same profiles as Gentoo thus Funtoo/2008.0 was strictly the same thing as Gentoo/2008.0 or the barely the same 10.0. This (monolithic) profile was set though a symbolic link named '''/etc/make.profile''' pointing on a complex directory architecture located somewhere under '''/usr/portage/profiles'''. This is no longer valid with the Funtoo 1.0 profiles as they are split in several smaller bricks which are then glued together via the  '''/etc/portage/make.profile/parent''' file (You do not need to include everything, just use the "bricks" you need). Those bricks belongs to several categories:
  
−
=== Upgrade to the Development Version of Portage ===
+
1. MANDATORY -- An "arch" profile which defines settings for a particular architecture. You'll want to set this to whatever arch your system is and leave it alone. '''Setting it to a different arch than your system could severely break it.'''
  
−
The new profile uses the development version of portage which is currently masked.
+
2. MANDATORY -- A "build" profile which should match the tree you wish to use. '''Stable''', '''Current''' (~arch), or '''Experimental''' (use it if you are brave enough and find '''current''' too stable).
  
−
If you use /etc/portage/package.{keywords,mask,unmask,use} as folders you can unmask it like so:
+
3. MANDATORY -- A "flavor" profile (what was previously known as ''profiles'' is still known as such in Gentoo) which describes the kind of system you want.
 +
* minimal - Be warned, minimal is exactly what it says, the minimal profile stuff you need for a usable system, nothing else. This is really for people who know what they're doing.
 +
* core - This is the core profile. This is for stuff that affects both desktops and servers.
 +
* desktop - Exactly what it says. If you're using a desktop, you should set this as your flavor.
 +
* server - If you're running a server, you should set this as your flavor.
  
−
<pre>
+
4. OPTIONAL -- One or more "mix-ins" profiles which describe optional add-ons. 'mix-ins' are the heart of the Funtoo 1.0 profiles. Unlike the monolithic profiles which sets a massive amount of use flags and options for you, we've split them into logical add-on profiles. For instance if you want support for gnome, you would add the gnome mix-in to your current profiles. That mix-in sets all the proper use flags and such for gnome. Same with others. Want dvd support? Add that one in. Using a rhel5 kernel which requires special versions of packages such as udev? There's a mix-in for that too. Run a mail server? web server? There's mix-ins for those also. Expect this category to grow in the future as new mix-ins are created.
−
echo ">=sys-portage/portage-9999" > /etc/portage/package.unmask/portage
+
−
echo ">=sys-portage/portage-9999 **" > /etc/portage/package.keywords/portage
+
−
</pre>
+
  
−
If you use /etc/portage/package.{keywords,mask,unmask,use} as files you can unmask it like so:
+
The contents of '''/etc/portage/make.profile/parent''' for a basic setup might look like this:
  
 
<pre>
 
<pre>
−
echo ">=sys-portage/portage-9999" >> /etc/portage/package.unmask
+
gentoo:funtoo/1.0/linux-gnu/arch/x86-64bit
−
echo ">=sys-portage/portage-9999 **" >> /etc/portage/package.keywords
+
gentoo:funtoo/1.0/linux-gnu/build/current
 +
gentoo:funtoo/1.0/linux-gnu/flavor/core
 
</pre>
 
</pre>
  
−
Now you can update portage:
+
A more rounded setup for a desktop might look like this:
  
 
<pre>
 
<pre>
−
emerge -va =portage-9999
+
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
 
</pre>
 
</pre>
  
−
=== Move the make.conf file ===
+
=== Using eselect ===
−
 
+
The preferred method of adding and removing profiles is to use [[eselect|eselect profile]]. This ensures that profiles are added correctly and in the proper order. The order is very important for things to work right.
 +
For a list of options, run:
 
<pre>
 
<pre>
−
mv /etc/make.conf /etc/portage/make.defaults
+
# eselect profile help
 
</pre>
 
</pre>
  
−
=== Define the PORTDIR, DISTDIR and PKGDIR locations ===
+
As stated by the previous command output, let's see the list of what profiles currently defined the option '''list''':
−
 
+
−
As per a prior discussion The Funtoo Core Team has decided to change the default PORTDIR, DISTDIR and PKGDIR locations from:
+
  
 
<pre>
 
<pre>
−
/usr/portage
+
# eselect profile list
−
/usr/portage/distfiles
+
Currently available arch profiles:
−
/usr/portage/packages
+
  [1]  funtoo/1.0/linux-gnu/arch/x86-64bit *
 +
Currently available build profiles:
 +
  [2]  funtoo/1.0/linux-gnu/build/stable
 +
  [3]  funtoo/1.0/linux-gnu/build/current *
 +
  [4]  funtoo/1.0/linux-gnu/build/experimental
 +
Currently available flavor profiles:
 +
  [5]  funtoo/1.0/linux-gnu/flavor/minimal
 +
  [6]  funtoo/1.0/linux-gnu/flavor/core
 +
  [7]  funtoo/1.0/linux-gnu/flavor/desktop *
 +
Currently available mix-ins profiles:
 +
  [8]  funtoo/1.0/linux-gnu/mix-ins/dvd
 +
  [9]  funtoo/1.0/linux-gnu/mix-ins/gnome
 +
  [10]  funtoo/1.0/linux-gnu/mix-ins/kde
 +
  [11]  funtoo/1.0/linux-gnu/mix-ins/media
 +
  [12]  funtoo/1.0/linux-gnu/mix-ins/rhel5-compat
 +
  [13]  funtoo/1.0/linux-gnu/mix-ins/server-db
 +
  [14]  funtoo/1.0/linux-gnu/mix-ins/server-mail
 +
  [15]  funtoo/1.0/linux-gnu/mix-ins/server-web
 +
  [16]  funtoo/1.0/linux-gnu/mix-ins/workstation
 +
  [17]  funtoo/1.0/linux-gnu/mix-ins/workstation-minimal
 
</pre>
 
</pre>
  
−
to:
+
As in several other Funtoo utilities, a star on the right indicates an active item (your case may differ from the example above). To add, say, the mix-ins '''dvd''', '''kde''' and '''media''' you have to enter:
  
 
<pre>
 
<pre>
−
/var/cache/portage
+
# eselect profile add 8
−
/var/src/distfiles
+
# eselect profile add 10
−
/var/cache/portage/packages
+
# eselect profile add 11
 
</pre>
 
</pre>
  
−
You may prefer the old or a custom directory structure or simply not wish to currently be bothered with moving things around. If so, you need to explicting define the DISTDIR and PKGDIR locations in the /etc/portage/make.defaults file like so:
+
Or in a one-shot:
  
 
<pre>
 
<pre>
−
DISTDIR="/usr/portage/distfiles"
+
# eselect profile add 8 10 11
−
PKGDIR="/usr/portage/packages"
+
 
</pre>
 
</pre>
  
−
The PORTDIR location must also be defined It has moved to a new file and can be set like so:
+
Verification:
  
 
<pre>
 
<pre>
−
echo "/usr/portage" > /etc/portage/portdir
+
# eselect profile list 
 +
Currently available arch profiles:
 +
  [1]  funtoo/1.0/linux-gnu/arch/x86-64bit *
 +
Currently available build profiles:
 +
  [2]  funtoo/1.0/linux-gnu/build/stable
 +
  [3]  funtoo/1.0/linux-gnu/build/current *
 +
  [4]  funtoo/1.0/linux-gnu/build/experimental
 +
Currently available flavor profiles:
 +
  [5]  funtoo/1.0/linux-gnu/flavor/minimal
 +
  [6]  funtoo/1.0/linux-gnu/flavor/core
 +
  [7]  funtoo/1.0/linux-gnu/flavor/desktop *
 +
Currently available mix-ins profiles:
 +
  [8]  funtoo/1.0/linux-gnu/mix-ins/dvd *
 +
  [9]  funtoo/1.0/linux-gnu/mix-ins/gnome
 +
  [10]  funtoo/1.0/linux-gnu/mix-ins/kde *
 +
  [11]  funtoo/1.0/linux-gnu/mix-ins/media *
 +
  [12]  funtoo/1.0/linux-gnu/mix-ins/rhel5-compat
 +
  [13]  funtoo/1.0/linux-gnu/mix-ins/server-db
 +
  [14]  funtoo/1.0/linux-gnu/mix-ins/server-mail
 +
  [15]  funtoo/1.0/linux-gnu/mix-ins/server-web
 +
  [16]  funtoo/1.0/linux-gnu/mix-ins/workstation
 +
  [17]  funtoo/1.0/linux-gnu/mix-ins/workstation-minimal
 
</pre>
 
</pre>
  
−
=== Define your overlays ===
+
{{fancywarning|You must use the numbers to reference the profiles bits you want.}}
  
−
If you use layman you can just copy its make.conf and edit out the unnecessary lines accordingly.
+
No magic here, what you add is put by portage in the /etc/portage/make.profile/parent file. In the present case this file contains:
  
 
<pre>
 
<pre>
−
cp -a /var/lib/layman/make.conf > /etc/portage/overlays
+
# cat /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/gnome
 +
gentoo:funtoo/1.0/linux-gnu/mix-ins/kde
 +
gentoo:funtoo/1.0/linux-gnu/mix-ins/media
 
</pre>
 
</pre>
  
−
Once done, you can append any additional overlays as needed:
+
=== Finish Up ===
−
 
+
{{fancynote|Removing the /etc/make.profile symlink is only necessary if the auto-upgrade script failed and you are manually switching profiles. Otherwise the /etc/make.profile symlink should already be removed}}
 +
Before updating with your new profiles, you'll need to remove the /etc/make.profile symlink if it exists otherwise portage will continue using the old profile.
 
<pre>
 
<pre>
−
echo "/usr/local/portage" >> /etc/portage/overlays
+
rm /etc/make.profile
 
</pre>
 
</pre>
  
−
=== Define the profile sub-sets you will use ===
+
Then update world using the new profiles.
−
 
+
−
A feature of the Funtoo 1.0 profile is the /etc/portage/parent file which describes what profiles your specific system derives settings from. It is made up of 4 components:
+
−
 
+
−
1. A "arch" profile which defines settings for a particular architecture.
+
−
 
+
−
2. A "build" profile which describes the intent of ACCEPT_KEYWORDS variable in the /etc/portage/make.defaults file.
+
−
 
+
−
3. A "flavor" profile (what was previously known as profiles) which desrcibes the kind of system you want.
+
−
 
+
−
4. One more "mix-ins" profiles which describe optional add-ons.
+
−
 
+
−
A minimalistic setup might look like this:
+
−
 
+
−
<pre>
+
−
:funtoo/1.0/linux-gnu/arch/x86-64bit
+
−
:funtoo/1.0/linux-gnu/build/current
+
−
:funtoo/1.0/linux-gnu/flavor/core
+
−
</pre>
+
−
 
+
−
A more rounded setup might look like this:
+
−
 
+
−
<pre>
+
−
:funtoo/1.0/linux-gnu/arch/x86-64bit
+
−
:funtoo/1.0/linux-gnu/build/current
+
−
:funtoo/1.0/linux-gnu/flavor/desktop
+
−
:funtoo/1.0/linux-gnu/mix-ins/dvd
+
−
:funtoo/1.0/linux-gnu/mix-ins/media
+
−
</pre>
+
−
 
+
−
=== Define the EAPI version ===
+
−
 
+
−
{{fancyimportant|Omitting this step will cause emerge to complain about slots in masks and so on.}}
+
−
 
+
−
<pre>
+
−
echo "4" > /etc/portage/eapi
+
−
</pre>
+
−
 
+
−
=== Finish Up ===
+
−
 
+
 
<pre>
 
<pre>
 
emerge -vauDN world
 
emerge -vauDN world
Line 206: Line 184:
 
Inspect the output of the prior command carefully. It is entirely possible that the use flags of several packages have changed. Many were removed in an effort to stay minimalistic.
 
Inspect the output of the prior command carefully. It is entirely possible that the use flags of several packages have changed. Many were removed in an effort to stay minimalistic.
  
−
For instance, gcc will no longer have the fortran use enabled flag by default and libreoffice/openoffice will no longer have the cups use flag enabled by default.
+
For instance, libreoffice/openoffice will no longer have the cups use flag enabled by default.
  
−
Adjust your system-wide and application-specific use flags as necessary then re-run the prior command and update when stratified.
+
Adjust your system-wide and application-specific use flags as necessary then re-run the prior command and update when satisfied.
  
−
= Dealing with the Leftovers =
+
== Related ==
 +
* [[Flavors and Mix-ins]]
  
−
== Remove Obsoleted Variables From /etc/portage/make.defaults ==
+
[[Category:Funtoo features]]
−
 
+
−
<pre>
+
−
SYNC                        Superseded by internal funtoo portage tracking.
+
−
PORTDIR_OVERLAY            Superseded by the /etc/portage/portdir file.
+
−
SOURCE                      Superseded by the /etc/portage/overlays file.
+
−
</pre>
+
−
 
+
−
== Remove Obsoleted Files From /etc/ ==
+
−
 
+
−
<pre>
+
−
/etc/make.conf              Superseded by the /etc/portage/make.defaults file.
+
−
/etc/make.conf.example      If anything a /etc/portage/make.defaults.examples needs to be created.
+
−
/etc/make.globals          [TODO: Find out if this is needed]
+
−
/etc/make.profile          Superseded by the /etc/portage/parent file.
+
−
</pre>
+
−
 
+
−
= Gotchas =
+
−
 
+
−
== eselect profile ==
+
−
 
+
−
The eselect profile <action> <options> command no longer works and furthermore is no longer relevant.
+
−
 
+
−
== layman ==
+
−
 
+
−
The /etc/portage/make.defaults file does not support sourcing external files. You must list your overlays in the /etc/portage/overlays file as illustrated above.
+
−
 
+
−
== eix ==
+
−
 
+
−
The current version of eix does not support the new profile. Until this issue is resolved you can use the following work-around which involves bringing the /etc/make.conf file back from the dead:
+
−
 
+
−
<pre>
+
−
echo "source /var/lib/layman/make.conf" > /etc/make.conf
+
−
</pre>
+

Revision as of 07:44, 18 November 2012

Contents

What It Is

The main idea behind the Funtoo 1.0 Profile is to do away with the current monolithic "one size fits all" approach. Instead of setting one massive profile and then overriding whatever you don't want, the Funtoo 1.0 Profile uses a new multi profile approach which allows way more flexibility and customization. Instead of having to remove what you don't want, now you'll be able to add in just the parts that you do want and leave out the rest.

How It Works

Please check Funtoo 1.0 Profile: Internals(Coming Soon).

What It Looks Like

Here's a what a list of profiles looks like: 

starmine portage # eselect profile list
Currently available arch profiles:
  [1]   funtoo/1.0/linux-gnu/arch/x86-32bit
  [2]   funtoo/1.0/linux-gnu/arch/x86-64bit
Currently available build profiles:
  [3]   funtoo/1.0/linux-gnu/build/stable
  [4]   funtoo/1.0/linux-gnu/build/current
  [5]   funtoo/1.0/linux-gnu/build/experimental
Currently available flavor profiles:
  [6]   funtoo/1.0/linux-gnu/flavor/minimal
  [7]   funtoo/1.0/linux-gnu/flavor/core
  [8]   funtoo/1.0/linux-gnu/flavor/desktop
  [9]   funtoo/1.0/linux-gnu/flavor/workstation
Currently available mix-ins profiles:
  [10]   funtoo/1.0/linux-gnu/mix-ins/audio
  [11]  funtoo/1.0/linux-gnu/mix-ins/console-extras
  [12]  funtoo/1.0/linux-gnu/mix-ins/dvd
  [13]  funtoo/1.0/linux-gnu/mix-ins/gnome
  [14]  funtoo/1.0/linux-gnu/mix-ins/kde
  [15]  funtoo/1.0/linux-gnu/mix-ins/media
  [16]  funtoo/1.0/linux-gnu/mix-ins/print
  [17]  funtoo/1.0/linux-gnu/mix-ins/python3-only
  [18]  funtoo/1.0/linux-gnu/mix-ins/rhel5-compat
  [19]  funtoo/1.0/linux-gnu/mix-ins/server-db
  [20]  funtoo/1.0/linux-gnu/mix-ins/server-mail
  [21]  funtoo/1.0/linux-gnu/mix-ins/server-web
  [22]  funtoo/1.0/linux-gnu/mix-ins/X
  [23]  funtoo/1.0/linux-gnu/mix-ins/xfce

As you can see, there are multiple types of profiles to choose from. Let's move on to how to start using it.

Switch to the Funtoo 1.0 Profile

Define the profile sub-sets you will use

So far in Funtoo we have used the exact same profiles as Gentoo thus Funtoo/2008.0 was strictly the same thing as Gentoo/2008.0 or the barely the same 10.0. This (monolithic) profile was set though a symbolic link named /etc/make.profile pointing on a complex directory architecture located somewhere under /usr/portage/profiles. This is no longer valid with the Funtoo 1.0 profiles as they are split in several smaller bricks which are then glued together via the /etc/portage/make.profile/parent file (You do not need to include everything, just use the "bricks" you need). Those bricks belongs to several categories:

1. MANDATORY -- An "arch" profile which defines settings for a particular architecture. You'll want to set this to whatever arch your system is and leave it alone. Setting it to a different arch than your system could severely break it.

2. MANDATORY -- A "build" profile which should match the tree you wish to use. Stable, Current (~arch), or Experimental (use it if you are brave enough and find current too stable).

3. MANDATORY -- A "flavor" profile (what was previously known as profiles is still known as such in Gentoo) which describes the kind of system you want.

  • minimal - Be warned, minimal is exactly what it says, the minimal profile stuff you need for a usable system, nothing else. This is really for people who know what they're doing.
  • core - This is the core profile. This is for stuff that affects both desktops and servers.
  • desktop - Exactly what it says. If you're using a desktop, you should set this as your flavor.
  • server - If you're running a server, you should set this as your flavor.

4. OPTIONAL -- One or more "mix-ins" profiles which describe optional add-ons. 'mix-ins' are the heart of the Funtoo 1.0 profiles. Unlike the monolithic profiles which sets a massive amount of use flags and options for you, we've split them into logical add-on profiles. For instance if you want support for gnome, you would add the gnome mix-in to your current profiles. That mix-in sets all the proper use flags and such for gnome. Same with others. Want dvd support? Add that one in. Using a rhel5 kernel which requires special versions of packages such as udev? There's a mix-in for that too. Run a mail server? web server? There's mix-ins for those also. Expect this category to grow in the future as new mix-ins are created.

The contents of /etc/portage/make.profile/parent for a basic setup might look like this: 

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

A more rounded setup for a desktop might look like this: 

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

Using eselect

The preferred method of adding and removing profiles is to use eselect profile. This ensures that profiles are added correctly and in the proper order. The order is very important for things to work right. For a list of options, run: 

# eselect profile help

As stated by the previous command output, let's see the list of what profiles currently defined the option list: 

# eselect profile list
Currently available arch profiles:
  [1]   funtoo/1.0/linux-gnu/arch/x86-64bit *
Currently available build profiles:
  [2]   funtoo/1.0/linux-gnu/build/stable
  [3]   funtoo/1.0/linux-gnu/build/current *
  [4]   funtoo/1.0/linux-gnu/build/experimental
Currently available flavor profiles:
  [5]   funtoo/1.0/linux-gnu/flavor/minimal
  [6]   funtoo/1.0/linux-gnu/flavor/core
  [7]   funtoo/1.0/linux-gnu/flavor/desktop *
Currently available mix-ins profiles:
  [8]   funtoo/1.0/linux-gnu/mix-ins/dvd
  [9]   funtoo/1.0/linux-gnu/mix-ins/gnome
  [10]  funtoo/1.0/linux-gnu/mix-ins/kde
  [11]  funtoo/1.0/linux-gnu/mix-ins/media
  [12]  funtoo/1.0/linux-gnu/mix-ins/rhel5-compat
  [13]  funtoo/1.0/linux-gnu/mix-ins/server-db
  [14]  funtoo/1.0/linux-gnu/mix-ins/server-mail
  [15]  funtoo/1.0/linux-gnu/mix-ins/server-web
  [16]  funtoo/1.0/linux-gnu/mix-ins/workstation
  [17]  funtoo/1.0/linux-gnu/mix-ins/workstation-minimal

As in several other Funtoo utilities, a star on the right indicates an active item (your case may differ from the example above). To add, say, the mix-ins dvd, kde and media you have to enter: 

# eselect profile add 8
# eselect profile add 10
# eselect profile add 11

Or in a one-shot: 

# eselect profile add 8 10 11

Verification: 

# eselect profile list  
Currently available arch profiles:
  [1]   funtoo/1.0/linux-gnu/arch/x86-64bit *
Currently available build profiles:
  [2]   funtoo/1.0/linux-gnu/build/stable
  [3]   funtoo/1.0/linux-gnu/build/current *
  [4]   funtoo/1.0/linux-gnu/build/experimental
Currently available flavor profiles:
  [5]   funtoo/1.0/linux-gnu/flavor/minimal
  [6]   funtoo/1.0/linux-gnu/flavor/core
  [7]   funtoo/1.0/linux-gnu/flavor/desktop *
Currently available mix-ins profiles:
  [8]   funtoo/1.0/linux-gnu/mix-ins/dvd *
  [9]   funtoo/1.0/linux-gnu/mix-ins/gnome
  [10]  funtoo/1.0/linux-gnu/mix-ins/kde *
  [11]  funtoo/1.0/linux-gnu/mix-ins/media *
  [12]  funtoo/1.0/linux-gnu/mix-ins/rhel5-compat
  [13]  funtoo/1.0/linux-gnu/mix-ins/server-db
  [14]  funtoo/1.0/linux-gnu/mix-ins/server-mail
  [15]  funtoo/1.0/linux-gnu/mix-ins/server-web
  [16]  funtoo/1.0/linux-gnu/mix-ins/workstation
  [17]  funtoo/1.0/linux-gnu/mix-ins/workstation-minimal

You must use the numbers to reference the profiles bits you want.


No magic here, what you add is put by portage in the /etc/portage/make.profile/parent file. In the present case this file contains: 

# cat /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/gnome
gentoo:funtoo/1.0/linux-gnu/mix-ins/kde
gentoo:funtoo/1.0/linux-gnu/mix-ins/media

Finish Up

Removing the /etc/make.profile symlink is only necessary if the auto-upgrade script failed and you are manually switching profiles. Otherwise the /etc/make.profile symlink should already be removed


Before updating with your new profiles, you'll need to remove the /etc/make.profile symlink if it exists otherwise portage will continue using the old profile. 

rm /etc/make.profile

Then update world using the new profiles. 

emerge -vauDN world

Inspect the output of the prior command carefully. It is entirely possible that the use flags of several packages have changed. Many were removed in an effort to stay minimalistic.

For instance, libreoffice/openoffice will no longer have the cups use flag enabled by default.

Adjust your system-wide and application-specific use flags as necessary then re-run the prior command and update when satisfied.

Related

Retrieved from "http://www.funtoo.org/index.php?title=Funtoo_1.0_Profile&oldid=8056"
Personal tools
Namespaces

Variants
Actions
Categories
Toolbox
Stuff