Difference between revisions of "Funtoo 1.0 Profile"
From Funtoo Linux
(→The main idea) |
(→The files inside /etc/portage) |
||
| Line 8: | Line 8: | ||
== The files inside /etc/portage == | == The files inside /etc/portage == | ||
| − | + | 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: | |
| − | {| | + | * single a flat file (one statement per line) |
| + | * a directory containing several files (those are sorted in alphabetical order then "summed" as if they were a single file) | ||
| + | |||
| + | {|- | ||
! File-/Dir-name | ! File-/Dir-name | ||
| − | |||
! Function | ! Function | ||
|- | |- | ||
| bin | | bin | ||
| − | |||
| autocreated, normally no need to edit | | autocreated, normally no need to edit | ||
|- | |- | ||
| package.accept_keywords | | package.accept_keywords | ||
| − | |||
| for packages where you like to accecpt other keywords too | | for packages where you like to accecpt other keywords too | ||
|- | |- | ||
| package.env | | package.env | ||
| − | | | + | | Entries (one per package atom) refer to environment files that are placed in the '''/etc/portage/env''' directory (see below). |
| − | + | ||
|- | |- | ||
| package.keywords | | 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 | | package.license | ||
| − | |||
| for unmasking special licenses per package | | for unmasking special licenses per package | ||
|- | |- | ||
| package.mask | | package.mask | ||
| − | |||
| for masking special packages or special package versions | | for masking special packages or special package versions | ||
|- | |- | ||
| package.properties | | package.properties | ||
| − | |||
| | | | ||
|- | |- | ||
| package.unmask | | package.unmask | ||
| − | |||
| unmasking special package-version that have been masked by Developers | | unmasking special package-version that have been masked by Developers | ||
|- | |- | ||
| package.use | | package.use | ||
| − | |||
| setting per package USE-Flags | | setting per package USE-Flags | ||
|- | |- | ||
| postsync.d | | postsync.d | ||
| − | |||
| autogenerated, normaly no need to edit | | autogenerated, normaly no need to edit | ||
|- | |- | ||
| savedconfig | | savedconfig | ||
| − | |||
| Storage for configs that need to be included while building a special package | | Storage for configs that need to be included while building a special package | ||
|- | |- | ||
| make.defaults | | make.defaults | ||
| − | |||
| The former /etc/make.conf file all settings you had in there will be in here now | | The former /etc/make.conf file all settings you had in there will be in here now | ||
|- | |- | ||
| overlays | | overlays | ||
| − | |||
| That file defines the overlays for you | | That file defines the overlays for you | ||
|- | |- | ||
| parent | | parent | ||
| − | |||
| here you choose what profile you will use | | here you choose what profile you will use | ||
|- | |- | ||
| portdir | | 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 | | 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 | ||
|- | |- | ||
Revision as of 01:12, 17 May 2011
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
The main idea
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 /etc/make.conf, /etc/make.profile-symlinking and /etc/portage). All the configuration is now done inside of /etc/portage. Also the profile structure in itself has been revised to bring simplicity without sacrificing the Funtoo flexibility.
The files inside /etc/portage
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:
- single a flat file (one statement per line)
- a directory containing several files (those are sorted in alphabetical order then "summed" as if they were a single file)
| File-/Dir-name | Function |
|---|---|
| bin | autocreated, normally no need to edit |
| package.accept_keywords | for packages where you like to accecpt 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
/etc/portage/package.env
/etc/portage/package.keywords
/etc/portage/package.license
/etc/portage/package.mask
/etc/portage/package.properties
/etc/portage/package.unmask
/etc/portage/package.use
/etc/portage/savedconfig
/etc/portage/make.defaults
/etc/portage/overlays
Example overlay file
oleg@orion ~ $ cat /etc/portage/overlays /var/lib/layman/lcd-filtering /var/lib/layman/mpd /var/lib/layman/oss-overlay /home/oleg/funtoo-overlay
/etc/portage/parent
Example profile
oleg@orion ~ $ cat /etc/portage/parent #:default/linux/amd64/2008.0 :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
/etc/portage/portdir
Example portage tree
oleg@orion ~ $ cat /etc/portage/portdir /var/cache/portage
