Difference between pages "Repository Configuration" and "Talk:Intel64-haswell"

(Difference between pages)
(Migrating existing configurations)
 
(Suggestion to add the "LZCNT" flag to CPU_FLAGS_X86)
 
Line 1: Line 1:
{{Warning|This article is a work-in-progress referring to a future Portage version. It does not apply to the current Funtoo Portage version. Please do not update your configuration yet.}}
+
Should the CPU_FLAGS suggested on this page include "lzcnt"?
 +
As listed here [1] lzcnt was adopted in Intel Haswell.
  
Starting with Portage-2.3.8, a switch to a new repository configuration framework is complete and users may want to update their configuration files. This document aims to describe the goals for the new framework and how to use it.
+
Or is there a special reason that LZCNT was not listed on this page?
  
== Multiple repository layout ==
+
[1] http://www.funtoo.org/CPU_FLAGS
One of the most important changes is the switch from the old ''overlay'' layout to a new cleaner ''repository'' system. The new layout is more flexible and more predictable. For example, repositories can now use resources (eclasses, for example) provided by other repositories.
+
 
+
The old layout was based on the concept of one ''main tree'' and optionally a number of overlays. The main tree provided base system ebuilds, eclasses, profiles, while overlays mostly were able to provide their own ebuilds. The ebuild provided by overlays overrode the ebuilds in main tree to the extend of making it impossible to install the main tree version. Overlays could also provide eclasses for their own ebuilds and package.* entries that applied to all overlays and to the main tree. The Package Manager is responsible for updating the main tree, while overlays are managed externally.
+
 
+
The new layout is based on the concept of one or more configurable repositories. Each repository can either be stand-alone or depend upon other repositories. The distribution provides a repository called ''funtoo'' (a drop-in replacement for Gentoo's ''gentoo'' repository). Users can install more repositories at they will, the repositories providing their own ebuilds, eclasses and profiles as necessary and/or using them from other repositories. Users can explicitly choose the repository they want to install packages from. The Package Manager can update all repositories.
+
 
+
== Portage configuration ==
+
=== New repository layout ===
+
The repository configuration should be stored in <code>/etc/portage/repos.conf</code>. It can be either a single file or a directory containing one or more ''.conf'' files.
+
 
+
The default configuration is installed as <code>/usr/share/portage/config/repos.conf</code>. This file is internal configuration file installed with portage ebuild and should '''not''' be modified. Instead, the configuration in <code>/etc/portage/repos.conf</code> can override the defaults specified there.
+
 
+
The configuration uses format similar to Windows .ini files. Each section heading (repository name in square brackets) signifies a single repository, followed by one or more key-value option pairs. For example, the following file copies default configuration for Funtoo repository:
+
 
+
{{file|name=/etc/portage/repos.conf/funtoo.conf|desc=Example configuration override for Funtoo repository to move it to non-standard location|body=
+
[funtoo]
+
# moved to non-standard location!
+
location = /var/db/repos/funtoo
+
sync-type = git
+
sync-uri = git://github.com/funtoo/ports-2015.git
+
auto-sync = yes
+
}}
+
 
+
The most useful repository configuration options are listed below:
+
;location: ''Obligatory.'' Specifies the directory where repository is/will be stored. If Portage knows how to sync the repository and the location does not exist, it will be created on next ''emerge --sync''. Otherwise, the directory must exist.
+
;priority: Specifies the priority used for ordering ebuilds from different repositories. If two repositories provide an ebuild with matching versions, the repository with higher priority will be used.
+
;auto-sync: Specifies whether ''emerge --sync'' should update the repository. Defaults to ''yes'' if ''sync-type'' is specified, ''no'' otherwise.
+
;sync-depth: Specifies ''--depth'' for git clone. Used only on initial sync. Defaults to 1. Can be set to 0 to force full clone (not pass ''--depth'' at all).
+
;sync-type: Specifies syncing/update method. Can be one of: ''cvs'', ''git'', ''rsync'', ''svn''.
+
;sync-umask: Specifies the umask used when updating/syncing the repository.
+
;sync-uri: Specifies remote URI from which the repository will be cloned/synced. Can use any syntax valid for a particular syncing method.
+
;sync-user: Specifies the user[:group] used to update/sync the repository. If ''FEATURES=usersync'' is used, defaults to the credentials of directory owner.
+
 
+
Additionally a <code>[DEFAULT]</code> section may be specified. Options in this section are used as defaults for all repositories.
+
 
+
=== Migrating existing configurations ===
+
The new configuration format provides replacement for existing configuration done through <code>/etc/portage/make.conf</code> and environment variables. While the variables are still supported for backwards compatibility, users are recommended to move to the new configuration scheme. Funtoo portage ebuild is planned to  make the migration unattended (repos.conf installed automatically to ease the config steps) with the following file:
+
+
{{file|name=/etc/portage/repos.conf/funtoo.conf|body=
+
[funtoo]
+
location = /usr/portage
+
sync-type = git
+
sync-uri = git://github.com/funtoo/ports-2015.git
+
auto-sync = yes
+
}}
+
The following replacements are provided for existing variables:
+
;PORTDIR: Used to specify main tree location. Replaced by ''location'' key in the section corresponding to the default repository (<code>[funtoo]</code> by default).
+
;PORTDIR_OVERLAY: Used to specify locations of overlays. Each of the paths needs to be replaced with a separate repository section, with the path placed in ''location'' key. Additionally, ''priority'' may be used to force specific ordering of ebuild overrides.
+
;SYNC: Used to specify URI for syncing the main repository, also implied a protocol for doing that. Replaced by the ''sync-uri'' and ''sync-type'' keys in the default repository section.
+
;SYNC_UMASK: Used to specify umask for syncing repositories. Replaced by ''sync-umask'' key in repository configuration. Can be specified in <code>[DEFAULT]</code> section to apply to all repositories.
+
;SYNC_USER: Used to specify user credentials for syncing repositories. Replaced by ''sync-user'' key in repository configuration. Can be specified in <code>[DEFAULT]</code> section to apply to all repositories.
+
 
+
{{file|name=/etc/portage/make.conf|desc=Example old make.conf file|body=
+
# user changed PORTDIR location
+
PORTDIR="/var/db/repos/funtoo"
+
PORTDIR_OVERLAY="/var/db/repos/foo /var/db/repos/bar"
+
 
+
SYNC="git://github.com/funtoo/ports-2015.git"
+
SYNC_USER="oleg"
+
SYNC_UMASK="022"
+
}}
+
 
+
{{file|name=/etc/portage/repos.conf|desc=Replacement repos.conf file|body=
+
[DEFAULT]
+
sync-user = oleg
+
sync-umask = 022
+
 
+
[funtoo]
+
location = /var/db/repos/funtoo
+
sync-type = git
+
sync-uri = git://github.com/funtoo/ports-2015.git
+
 
+
[foo]
+
location = /var/db/repos/foo
+
priority = 1
+
 
+
[bar]
+
location = /var/db/repos/bar
+
priority = 2
+
}}
+
 
+
The <code>repos.conf</code> configuration can be further extended with ''sync-type'' and ''sync-uri'' for overlays to get ''emerge --sync'' updating them automatically.
+
 
+
[[Category:Portage]]
+

Revision as of 19:24, May 9, 2015

Should the CPU_FLAGS suggested on this page include "lzcnt"? As listed here [1] lzcnt was adopted in Intel Haswell.

Or is there a special reason that LZCNT was not listed on this page?

[1] http://www.funtoo.org/CPU_FLAGS