Difference between revisions of "Funtoo 1.0 Profile"

From Funtoo Linux
Jump to: navigation, search
Line 2: Line 2:
 
[[Category:Labs]]
 
[[Category:Labs]]
 
[[Category:HOWTO]]
 
[[Category:HOWTO]]
−
{{Fancywarning|This is atm not useable please do not do the switch to it... }}
+
{{Fancywarning|Currently, this is still BETA and needs more testing.}}  
 
= 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 fit's 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.
+
Currently available mix-ins profiles:
−
postsync.d/             [...]
+
  [9]  funtoo/1.0/linux-gnu/mix-ins/dvd
−
profile/               [...]
+
  [10]  funtoo/1.0/linux-gnu/mix-ins/gnome
−
savedconfig/           Storage for configuration files that need to be included while building a special package.
+
  [11]  funtoo/1.0/linux-gnu/mix-ins/kde
 +
  [12]  funtoo/1.0/linux-gnu/mix-ins/media
 +
  [13]  funtoo/1.0/linux-gnu/mix-ins/rhel5-compat
 +
  [14] funtoo/1.0/linux-gnu/mix-ins/server-db
 +
  [15]  funtoo/1.0/linux-gnu/mix-ins/server-mail
 +
  [16]  funtoo/1.0/linux-gnu/mix-ins/server-web
 +
  [17] funtoo/1.0/linux-gnu/mix-ins/workstation
 +
  [18]  funtoo/1.0/linux-gnu/mix-ins/workstation-minimal
 
</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 ==
 
== Prepare the System ==
  
−
This is only applicable if you are using the "portage.git" or "portage-mini-2010.git" portage trees.
+
=== Install newest eselect ===
−
 
+
Make sure you install this before trying to switch your profile.  
−
=== 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>
 
<pre>
−
cd /usr
+
echo "=app-admin/eselect-1.3.1.1_beta2" >> /etc/portage/package.unmask
−
mv portage portage.old
+
emerge -1 eselect
 
</pre>
 
</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 ==
−
 
+
{{fancynote:Currently we plan on having future versions of the eselect ebuild automatically switch the user from using the /etc/make.profile symlink to using /etc/portage/make.defaults/parent file. Right now you must manually remove the /etc/make.profile link or portage will continue using it.}}
−
{{fancywarning|The Funtoo 1.0 Profile is still in development and should not be used in production environments! portage-9999 is based on outdated and partly broken repository, use it on your own risk!!}}
+
−
 
+
−
=== 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-apps/portage-9999" > /etc/portage/package.unmask/portage
+
−
echo ">=sys-apps/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-apps/portage-9999" >> /etc/portage/package.unmask
+
−
echo ">=sys-apps/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, DISTDIR and PKGDIR locations ===
+
−
 
+
−
As per a prior discussion The Funtoo Core Team has decided to change the default PORTDIR, DISTDIR and PKGDIR locations from:
+
−
 
+
−
<pre>
+
−
/usr/portage
+
−
/usr/portage/distfiles
+
−
/usr/portage/packages
+
−
</pre>
+
−
 
+
−
to:
+
−
 
+
−
<pre>
+
−
/var/cache/portage
+
−
/var/src/distfiles
+
−
/var/cache/portage/packages
+
−
</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:
+
−
 
+
−
<pre>
+
−
DISTDIR="/usr/portage/distfiles"
+
−
PKGDIR="/usr/portage/packages"
+
−
</pre>
+
−
 
+
−
The PORTDIR location must also be defined It has moved to a new file and can be set like so:
+
−
 
+
−
<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 ===
 
=== Define the profile sub-sets you will use ===

Revision as of 19:30, 25 May 2012

Currently, this is still BETA and needs more testing.


Contents

What It Is

The main idea behind the Funtoo 1.0 Profile is to do away with the current monolithic "one size fit's 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
Currently available mix-ins profiles:
  [9]   funtoo/1.0/linux-gnu/mix-ins/dvd
  [10]  funtoo/1.0/linux-gnu/mix-ins/gnome
  [11]  funtoo/1.0/linux-gnu/mix-ins/kde
  [12]  funtoo/1.0/linux-gnu/mix-ins/media
  [13]  funtoo/1.0/linux-gnu/mix-ins/rhel5-compat
  [14]  funtoo/1.0/linux-gnu/mix-ins/server-db
  [15]  funtoo/1.0/linux-gnu/mix-ins/server-mail
  [16]  funtoo/1.0/linux-gnu/mix-ins/server-web
  [17]  funtoo/1.0/linux-gnu/mix-ins/workstation
  [18]  funtoo/1.0/linux-gnu/mix-ins/workstation-minimal

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

Prepare the System

Install newest eselect

Make sure you install this before trying to switch your profile. 

echo "=app-admin/eselect-1.3.1.1_beta2" >> /etc/portage/package.unmask
emerge -1 eselect

Switch to the Funtoo 1.0 Profile

{{fancynote:Currently we plan on having future versions of the eselect ebuild automatically switch the user from using the /etc/make.profile symlink to using /etc/portage/make.defaults/parent file. Right now you must manually remove the /etc/make.profile link or portage will continue using it.}}

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 describes 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=4311"
Personal tools
Namespaces

Variants
Actions
Categories
Toolbox
Stuff