Difference between revisions of "Funtoo 1.0 Profile"

From Funtoo Linux
Jump to: navigation, search
(Modified the page to read more like an informative HOWTO as per the TODO list.)
Line 1: Line 1:
 
[[Category:Portage]]
 
[[Category:Portage]]
 
[[Category:Labs]]
 
[[Category:Labs]]
 +
[[Category:HOWTO]]
  
−
{{fancywarning|This Profile isn't ready at the moment, it is still in development but we started to provide here more info so you can get more firm with it}}
+
= What It Is =
−
__TOC__
+
  
−
== The main idea ==
+
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 simplify the life of a Funtoo system administrator by grouping everything at a single place (no more messing around with <tt>/etc/make.conf</tt>, <tt>/etc/make.profile</tt>-symlinking and <tt>/etc/portage</tt>). All the configuration is now done inside of <tt>/etc/portage</tt>. Also the profile structure in itself has been revised to bring simplicity without sacrificing the Funtoo flexibility.
+
<pre>
 +
/etc/make.conf
 +
/etc/make.profile (symlink)
 +
/etc/portage/
 +
</pre>
  
−
== The files inside /etc/portage ==
+
Into a single "system profile":
  
−
The new structure used in 1.0 profiles is somewhat similar with what you were used to but with little changes highlighted in bold. Also the duality (file/directory) of '''package.*''' (package.mask, package.keywords...) remains. This duality allows you to express''' package.*''' in two ways:
+
<pre>
 +
/etc/portage/
 +
</pre>
  
−
* single a flat file (one statement per line)
+
= How It Works =
−
* a directory containing several files (those are sorted in alphabetical order then "summed" as if they were a single file)
+
  
−
{|-
+
Please check [[Funtoo 1.0 Profile: Internals]].
−
! File-/Dir-name
+
−
! Function
+
−
|-
+
−
| bin
+
−
| autocreated, normally no need to edit
+
−
|-
+
−
| package.accept_keywords
+
−
| for packages where you like to accept other keywords too
+
−
|-
+
−
| package.env
+
−
| Entries (one per package atom) refer to environment files that are placed in the '''/etc/portage/env''' directory (see below).
+
−
|-
+
−
| package.keywords
+
−
| Entries (one per package atom) allows you to define additional processor architecture/Funtoo branch keywords (e.g. sparc, ~amd64...). Note the special keyword ** (double star) which means all possible processor architecture/Funtoo branches.
+
−
|-
+
−
| package.license
+
−
| for unmasking special licenses per package
+
−
|-
+
−
| package.mask
+
−
| for masking special packages or special package versions
+
−
|-
+
−
| package.properties
+
−
|
+
−
|-
+
−
| package.unmask
+
−
| unmasking special package-version that have been masked by Developers
+
−
|-
+
−
| package.use
+
−
| setting per package USE-Flags
+
−
|-
+
−
| postsync.d
+
−
| autogenerated, normaly no need to edit
+
−
|-
+
−
| savedconfig
+
−
| Storage for configs that need to be included while building a special package
+
−
|-
+
−
| make.defaults
+
−
| The former /etc/make.conf file all settings you had in there will be in here now
+
−
|-
+
−
| overlays
+
−
| That file defines the overlays for you
+
−
|-
+
−
| parent
+
−
| here you choose what profile you will use
+
−
|-
+
−
| portdir
+
−
| That file is very important, you need to define the path to your portdir in here else the new funtoo 1.0 profile won't work
+
−
|-
+
−
|}
+
  
−
=== /etc/portage/package.accept_keywords ===
+
= What It Looks Like =
  
−
=== /etc/portage/package.env ===
+
A finished /etc/portage directory contains the following files and directories:
  
−
=== /etc/portage/package.keywords ===
+
<pre>
 +
bin/                    [...]
 +
eapi                    Define the EAPI version to maintain Gentoo Linux compatibility.
 +
make.defaults          What was previously known as the /etc/make.conf file.
 +
overlays                Define overlays.
 +
package.env/           Define environment files (one package per atom).
 +
package.keywords/      Define accepted architecture/Funtoo branch keywords for individual packages.
 +
package.license/        Define accepted licenses for individual packages.
 +
package.mask/          Define masks for individual packages.
 +
package.properties/    [...]
 +
package.unmask/        Define unmasks for individual packages.
 +
package.use/            Define use flags for individual packages.
 +
parent                  Define the profile sub-sets you wish to use.
 +
portdir                Define the path to your portage directory.
 +
postsync.d/            [...]
 +
profile/                [...]
 +
savedconfig/            Storage for configuration files that need to be included while building a special package.
 +
</pre>
  
−
=== /etc/portage/package.license ===
+
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.
  
−
=== /etc/portage/package.mask ===
+
= How To Use It =
  
−
=== /etc/portage/package.properties ===
+
== Prepare the System ==
−
+
−
=== /etc/portage/package.unmask ===
+
  
−
=== /etc/portage/package.use ===
+
This is only applicable if you are using the "portage.git" or "portage-mini-2010.git" portage trees.
  
−
=== /etc/portage/savedconfig ===
+
=== Switch to the Latest Portage Tree ===
  
−
=== /etc/portage/make.defaults ===
+
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:
  
−
=== /etc/portage/overlays ===
 
−
Example overlay file
 
 
<pre>
 
<pre>
−
oleg@orion ~ $ cat /etc/portage/overlays
+
cd /usr
−
/var/lib/layman/lcd-filtering
+
mv portage portage.old
−
/var/lib/layman/mpd
+
−
/var/lib/layman/oss-overlay
+
−
/home/oleg/funtoo-overlay
+
 
</pre>
 
</pre>
  
−
=== /etc/portage/parent ===
+
3. Next, edit /etc/make.conf and remove any hard-coded SYNC= variable from
−
Example profile
+
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 ==
 +
 
 +
{{fancywarning|The Funtoo 1.0 Profile is still in development and should not be used in production environments!}}
 +
 
 +
=== Upgrade to the Development Version of Portage ===
 +
 
 +
The new profile uses the development version of portage which is currently masked.
 +
 
 +
If you use /etc/portage/package.{keywords,mask,unmask,use} as folders you can unmask it like so:
 +
 
 +
<pre>
 +
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:
 +
 
 +
<pre>
 +
echo ">=sys-portage/portage-9999" >> /etc/portage/package.unmask
 +
echo ">=sys-portage/portage-9999 **" >> /etc/portage/package.keywords
 +
</pre>
 +
 
 +
Now you can update portage:
 +
 
 +
<pre>
 +
emerge -va =portage-9999
 +
</pre>
 +
 
 +
=== Move the make.conf file ===
 +
 
 +
<pre>
 +
mv /etc/make.conf /etc/portage/make.defaults
 +
</pre>
 +
 
 +
=== Define the portdir location ===
 +
 
 +
{{fancyimportant|As per prior discussion The Funtoo Core Team has decided that /usr/portage directory should be at /var/cache/portage instead and that disfiles and packages directories should also move to /var/cache/distfiles and /var/cache/packages respectively.}}
 +
 
 +
<pre>
 +
echo "/usr/portage" > /etc/portage/portdir
 +
</pre>
 +
 
 +
=== Define your overlays ===
 +
 
 +
If you use layman you can just copy its make.conf and edit out the unnecessary lines accordingly.
 +
 
 +
<pre>
 +
cp -a /var/lib/layman/make.conf > /etc/portage/overlays
 +
</pre>
 +
 
 +
Once done, you can append any additional overlays as needed:
 +
 
 +
<pre>
 +
echo "/usr/local/portage" >> /etc/portage/overlays
 +
</pre>
 +
 
 +
=== Define the profile sub-sets you will use ===
 +
 
 +
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>
 
<pre>
−
oleg@orion ~ $ cat /etc/portage/parent
+
:funtoo/1.0/linux-gnu/arch/x86-64bit
−
#:default/linux/amd64/2008.0
+
:funtoo/1.0/linux-gnu/build/current
−
: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/flavor/desktop
 
:funtoo/1.0/linux-gnu/mix-ins/dvd
 
:funtoo/1.0/linux-gnu/mix-ins/dvd
 
:funtoo/1.0/linux-gnu/mix-ins/media
 
:funtoo/1.0/linux-gnu/mix-ins/media
 
</pre>
 
</pre>
−
=== /etc/portage/portdir ===
+
 
−
Example portage tree
+
=== 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>
 +
emerge -vauDN world
 +
</pre>
 +
 
 +
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.
 +
 
 +
Adjust your system-wide and application-specific use flags as necessary then re-run the prior command and update when stratified.
 +
 
 +
= Dealing with the Leftovers =
 +
 
 +
== Remove Obsoleted Variables From /etc/portage/make.defaults ==
 +
 
 +
<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>
 
<pre>
−
oleg@orion ~ $ cat /etc/portage/portdir
+
echo "source /var/lib/layman/make.conf" > /etc/make.conf
−
/var/cache/portage
+
 
</pre>
 
</pre>

Revision as of 08:10, 19 August 2011


Contents

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: 

/etc/make.conf
/etc/make.profile (symlink)
/etc/portage/

Into a single "system profile": 

/etc/portage/

How It Works

Please check Funtoo 1.0 Profile: Internals.

What It Looks Like

A finished /etc/portage directory contains the following files and directories: 

bin/                    [...]
eapi                    Define the EAPI version to maintain Gentoo Linux compatibility.
make.defaults           What was previously known as the /etc/make.conf file.
overlays                Define overlays.
package.env/            Define environment files (one package per atom).
package.keywords/       Define accepted architecture/Funtoo branch keywords for individual packages.
package.license/        Define accepted licenses for individual packages.
package.mask/           Define masks for individual packages.
package.properties/     [...]
package.unmask/         Define unmasks for individual packages.
package.use/            Define use flags for individual packages.
parent                  Define the profile sub-sets you wish to use.
portdir                 Define the path to your portage directory.
postsync.d/             [...]
profile/                [...]
savedconfig/            Storage for configuration files that need to be included while building a special package.

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.

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: 

cd /usr
mv portage portage.old

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

The Funtoo 1.0 Profile is still in development and should not be used in production environments!


Upgrade to the Development Version of Portage

The new profile uses the development version of portage which is currently masked.

If you use /etc/portage/package.{keywords,mask,unmask,use} as folders you can unmask it like so: 

echo ">=sys-portage/portage-9999" > /etc/portage/package.unmask/portage
echo ">=sys-portage/portage-9999 **" > /etc/portage/package.keywords/portage

If you use /etc/portage/package.{keywords,mask,unmask,use} as files you can unmask it like so: 

echo ">=sys-portage/portage-9999" >> /etc/portage/package.unmask
echo ">=sys-portage/portage-9999 **" >> /etc/portage/package.keywords

Now you can update portage: 

emerge -va =portage-9999

Move the make.conf file 

mv /etc/make.conf /etc/portage/make.defaults

Define the portdir location

As per prior discussion The Funtoo Core Team has decided that /usr/portage directory should be at /var/cache/portage instead and that disfiles and packages directories should also move to /var/cache/distfiles and /var/cache/packages respectively. 


echo "/usr/portage" > /etc/portage/portdir

Define your overlays

If you use layman you can just copy its make.conf and edit out the unnecessary lines accordingly. 

cp -a /var/lib/layman/make.conf > /etc/portage/overlays

Once done, you can append any additional overlays as needed: 

echo "/usr/local/portage" >> /etc/portage/overlays

Define the profile sub-sets you will use

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: 

:funtoo/1.0/linux-gnu/arch/x86-64bit
:funtoo/1.0/linux-gnu/build/current
:funtoo/1.0/linux-gnu/flavor/core

A more rounded setup might look like this: 

: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

Define the EAPI version

Omitting this step will cause emerge to complain about slots in masks and so on. 


echo "4" > /etc/portage/eapi

Finish Up 

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

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

Dealing with the Leftovers

Remove Obsoleted Variables From /etc/portage/make.defaults 

SYNC                        Superseded by internal funtoo portage tracking.
PORTDIR_OVERLAY             Superseded by the /etc/portage/portdir file.
SOURCE                      Superseded by the /etc/portage/overlays file.

Remove Obsoleted Files From /etc/ 

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

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: 

echo "source /var/lib/layman/make.conf" > /etc/make.conf
Retrieved from "http://www.funtoo.org/index.php?title=Funtoo_1.0_Profile&oldid=4303"
Personal tools
Namespaces

Variants
Actions
Categories
Toolbox
Stuff