注意：
The Funtoo Linux project has transitioned to "Hobby Mode" and this wiki is now read-only.
Difference between revisions of "Package:Portage (Funtoo)"
Jump to navigation
Jump to search
Threesixes (talk | contribs) m (add information about where logs are located.) |
|||
| (14 intermediate revisions by 6 users not shown) | |||
| Line 5: | Line 5: | ||
|Repository=Funtoo Overlay | |Repository=Funtoo Overlay | ||
}} | }} | ||
== Introduction == | === Introduction === | ||
Portage is the official package manager of Funtoo Linux. Daniel Robbins | [http://en.wikipedia.org/wiki/Portage_(software) Portage] is the official package manager of Funtoo Linux. Historically, Daniel Robbins has maintained a slightly modified version of Portage, although now many of the features pioneered in this version of Portage has been merged upstream by Zac Medico. Funtoo has recently started using an unmodified upstream Gentoo version of Portage. Funtoo's 2.4.1 Portage is equivalent to the upstream 2.2.26 version of Portage -- Funtoo has used different version numbers for historical reasons. | ||
== Portage Commands == | === Portage Commands === | ||
{{TableStart}} | |||
{{2ColHead|Command|Description}} | |||
{{2Col|{{c|[[emerge]]}}|high-level dependency-based package merge/unmerge tool}} | |||
{{2Col|{{c|[[ebuild]]}}|lower-level package build tool}} | |||
{{2Col|{{c|etc-update}}|Original tool to manage updates to /etc configuration files.}} | |||
{{2Col|{{c|dispatch-conf}}|Newer tool to manage updates to /etc configuration files.}} | |||
{{TableEnd}} | |||
== Portage Specifications == | === Portage Specifications === | ||
The latest progress and changes related to EAPI/PMS and Portage can often be found in the Gentoo Council meeting logs, which are listed on the [ | The latest progress and changes related to EAPI/PMS and Portage can often be found in the Gentoo Council meeting logs, which are listed on the [https://wiki.gentoo.org/wiki/Project:Council Gentoo Council page]. | ||
The latest PMS specification to be approved by the Gentoo Council is available: [http:// | The latest PMS specification to be approved by the Gentoo Council is available: [http://dev.gentoo.org/~ulm/pms/5/pms.pdf eapi-5-approved-2012-09-20]. The PMS specification is an attempt to codify the inner workings of Portage, and is authored by Stephen Bennett, Christian Faulhammer, Ciaran McCreesh and Ulrich Müller as a Gentoo-hosted project. | ||
== Portage Profiles == | === Portage Profiles === | ||
Portage uses [[Portage Profiles|profiles]] to define settings for various architectures and types of Funtoo/Gentoo systems. See the [[Portage Profiles]] page for detailed information on how Portage handles profiles. Look at [[Creating_Profiles]] to learn how to create them and at [[Funtoo_1.0_Profile]] to learn about the Funtoo 1.0 profile. | Portage uses [[Portage Profiles|profiles]] to define settings for various architectures and types of Funtoo/Gentoo systems. See the [[Portage Profiles]] page for detailed information on how Portage handles profiles. Look at [[Creating_Profiles]] to learn how to create them and at [[Funtoo_1.0_Profile]] to learn about the Funtoo 1.0 profile. | ||
== Portage Variables == | ===Portage Variables === | ||
Portage's behavior can be controlled by a number of configuration settings other variables that can be defined within the ebuild itself. In addition, a number of these variables are defined for the ebuild automatically by Portage. These variables are now documented on their own page: [[Portage Variables]]. | Portage's behavior can be controlled by a number of configuration settings other variables that can be defined within the ebuild itself. In addition, a number of these variables are defined for the ebuild automatically by Portage. These variables are now documented on their own page: [[Portage Variables]]. | ||
== Multiple ABI Support == | === Multiple ABI Support === | ||
Portage contains support for multiple ABIs (Application Binary Interfaces) co-existing on the same system. This functionality has been extensively documented and has been moved to its own page: [[Multiple ABI Support]]. | Portage contains support for multiple ABIs (Application Binary Interfaces) co-existing on the same system. This functionality has been extensively documented and has been moved to its own page: [[Multiple ABI Support]]. | ||
== Ebuild Functions == | === Ebuild Functions === | ||
An ebuild developer has the ability to define [[Ebuild Functions]] that define steps to perform during a particular part of the ebuild lifecycle. These steps are now documented on their own page: [[Ebuild Functions]]. | An ebuild developer has the ability to define [[Ebuild Functions]] that define steps to perform during a particular part of the ebuild lifecycle. These steps are now documented on their own page: [[Ebuild Functions]]. | ||
== Funtoo Portage Development == | === Funtoo Portage Development === | ||
The Funtoo Core Team is currently working on a general-purpose plug-in system so that the GNU info file regeneration, news update display, and scanning of files that need updating in /etc can be pulled out of the official Portage emerge code. In addition, this plug-in system will allow other types of things to be hooked into various phases of emerge. This will allow various new plug-ins to be developed and used on systems, such as periodic security checks, etc. | The Funtoo Core Team is currently working on a general-purpose plug-in system so that the GNU info file regeneration, news update display, and scanning of files that need updating in /etc can be pulled out of the official Portage emerge code. In addition, this plug-in system will allow other types of things to be hooked into various phases of emerge. This will allow various new plug-ins to be developed and used on systems, such as periodic security checks, etc. | ||
== Portage Logs == | === Portage Logs === | ||
Logs of portage actions can be found at <code>/var/log/emerge.log</code> & <code>/var/log/portage/elog/summary.log-(date the log is generated)</code> | Logs of portage actions can be found at <code>/var/log/emerge.log</code> & <code>/var/log/portage/elog/summary.log-(date the log is generated)</code> | ||
| Line 50: | Line 53: | ||
Add support for portage to understand which version of a particular app is the "active" version that it was built against, and record this information in /var/db/pkg. This can help to implement perl-cleaner-like support in Portage. | Add support for portage to understand which version of a particular app is the "active" version that it was built against, and record this information in /var/db/pkg. This can help to implement perl-cleaner-like support in Portage. | ||
== Funtoo Features/Changes == | === Funtoo Features/Changes === | ||
{{Note|Many of these features have been merged into Gentoo's upstream Portage.}} | |||
==== In Funtoo stable/current Portage ==== | |||
=== In Funtoo stable/current Portage === | |||
;emerge --sync from git | ;emerge --sync from git | ||
| Line 82: | Line 65: | ||
: The Funtoo version of Portage has replaced the BSD-only sed wrapper with a symlink. This will eventually be deprecated. The sed wrapper was a way to provide BSD systems with a "sed" command that could be used inside ebuilds that worked similarly to GNU sed. A PATH fix has been applied so that /bin/sed will be detected first anyway. | : The Funtoo version of Portage has replaced the BSD-only sed wrapper with a symlink. This will eventually be deprecated. The sed wrapper was a way to provide BSD systems with a "sed" command that could be used inside ebuilds that worked similarly to GNU sed. A PATH fix has been applied so that /bin/sed will be detected first anyway. | ||
; | ;thin-manifest | ||
:Funtoo's Portage supports a special mode of operation where Manifests only contain digests for distfiles and not for files in the Portage tree. This is to eliminate redundant digests since git already provides SHA1 digests. This feature | :Funtoo's Portage supports a special mode of operation where Manifests only contain digests for distfiles and not for files in the Portage tree. This is to eliminate redundant digests since git already provides SHA1 digests. This feature, previously called "mini-manifest", has been moved to a repo-specific option so you do not needed anymore in your {{/etc/portage/make.conf}}. (note: this has now been done, as "thin-manifest" functionality has been integrated into recent versions of Portage, and is being beta tested in Funtoo). Funtoo provides a special "thin-manifest" tree that is smaller than the full-size Portage tree, and is intended to be used instead of the mini-manifest feature. | ||
;preserve bindist through USE filtering | ;preserve bindist through USE filtering | ||
| Line 99: | Line 82: | ||
;xz-utils auto-dependency | ;xz-utils auto-dependency | ||
:There are several ebuilds in the Gentoo Portage repository that use .xz files but do not explicitly depend on xz-utils. A workaround has been added to ebuild.sh to add this dependency to metadata automatically if a .xz file exists in SRC_URI. This change is not yet in the official Portage sources but is being used on the Funtoo side when generating our git-based Portage trees. | :There are several ebuilds in the Gentoo Portage repository that use .xz files but do not explicitly depend on xz-utils. A workaround has been added to ebuild.sh to add this dependency to metadata automatically if a .xz file exists in SRC_URI. This change is not yet in the official Portage sources but is being used on the Funtoo side when generating our git-based Portage trees. | ||
==== In current development version (2.3.8) ==== | |||
;emerge-webrsync removed | |||
: Gentoo Portage supports already tree syncing method via downloading a .tar.bz2 file containing all the ebuilds. Funtoo supports git syncing only, so the relevant code is removed. | |||
;SYNC_UMASK, SYNC_USER support | |||
: SYNC_USER and SYNC_UMASK can be used to define the user account to use for cloning/syncing, as well as the umask to use. | |||
;pwconv & grpconv are run after emerge | |||
: Portage runs pwconv & grpconv post-emerge to ensure /etc/shadow and /etc/gshadow are valid. | |||
;preserve bindist through USE filtering | |||
: Normally, anything not in an ebuild's IUSE is stripped from the USE passed to ebuild.sh. This patch allows "bindist" to not be stripped, so it can be used as a means to disable pre-merge sanity checks that may exist in pkg_setup() and pkg_pretend() but will not otherwise affect the resultant build. If "bindist" will affect some functionality in the package, then it should be added to an ebuild's IUSE. This patch allows pkg_setup() and pkg_pretend() to look for "bindist", which indicates that the ebuild is being built for release, typically in an automated fashion, and thus runtime sanity checks that might otherwise run can be optionally skipped. This check is used by the udev-160-r1.ebuild to see if we should fail if we are merging udev on a system where the kernel will not support it. In Metro, this is not a big deal, but on a ''real'' production system, merging the udev on an incompatible system will render the kernel inoperable. | |||
;Dynamic SLOT support re-enabled | |||
: The ebuilds are allowed to change their SLOT value during build. | |||
[[Category:Projects]] | [[Category:Projects]] | ||
[[Category:Portage]] | [[Category:Portage]] | ||
{{EbuildFooter}} | {{EbuildFooter}} | ||
Latest revision as of 05:34, September 10, 2016
Portage (Funtoo)
Tip
We welcome improvements to this page. To edit this page, Create a Funtoo account. Then log in and then click here to edit this page. See our editing guidelines to becoming a wiki-editing pro.
Introduction
Portage is the official package manager of Funtoo Linux. Historically, Daniel Robbins has maintained a slightly modified version of Portage, although now many of the features pioneered in this version of Portage has been merged upstream by Zac Medico. Funtoo has recently started using an unmodified upstream Gentoo version of Portage. Funtoo's 2.4.1 Portage is equivalent to the upstream 2.2.26 version of Portage -- Funtoo has used different version numbers for historical reasons.
Portage Commands
| Command | Description |
|---|---|
emerge | high-level dependency-based package merge/unmerge tool |
ebuild | lower-level package build tool |
etc-update | Original tool to manage updates to /etc configuration files. |
dispatch-conf | Newer tool to manage updates to /etc configuration files. |
Portage Specifications
The latest progress and changes related to EAPI/PMS and Portage can often be found in the Gentoo Council meeting logs, which are listed on the Gentoo Council page.
The latest PMS specification to be approved by the Gentoo Council is available: eapi-5-approved-2012-09-20. The PMS specification is an attempt to codify the inner workings of Portage, and is authored by Stephen Bennett, Christian Faulhammer, Ciaran McCreesh and Ulrich Müller as a Gentoo-hosted project.
Portage Profiles
Portage uses profiles to define settings for various architectures and types of Funtoo/Gentoo systems. See the Portage Profiles page for detailed information on how Portage handles profiles. Look at Creating_Profiles to learn how to create them and at Funtoo_1.0_Profile to learn about the Funtoo 1.0 profile.
Portage Variables
Portage's behavior can be controlled by a number of configuration settings other variables that can be defined within the ebuild itself. In addition, a number of these variables are defined for the ebuild automatically by Portage. These variables are now documented on their own page: Portage Variables.
Multiple ABI Support
Portage contains support for multiple ABIs (Application Binary Interfaces) co-existing on the same system. This functionality has been extensively documented and has been moved to its own page: Multiple ABI Support.
Ebuild Functions
An ebuild developer has the ability to define Ebuild Functions that define steps to perform during a particular part of the ebuild lifecycle. These steps are now documented on their own page: Ebuild Functions.
Funtoo Portage Development
The Funtoo Core Team is currently working on a general-purpose plug-in system so that the GNU info file regeneration, news update display, and scanning of files that need updating in /etc can be pulled out of the official Portage emerge code. In addition, this plug-in system will allow other types of things to be hooked into various phases of emerge. This will allow various new plug-ins to be developed and used on systems, such as periodic security checks, etc.
Portage Logs
Logs of portage actions can be found at /var/log/emerge.log & /var/log/portage/elog/summary.log-(date the log is generated)
TODO
Add support to portage, so that when an ebuild is merged, the /var/db/pkg entry contains a list of all currently-installed versions of all ebuilds upon which that ebuild RDEPENDs. This, combined with a comprehensive set of past USE settings (may need to implement this too,) can be used to detect when an ebuild needs to be rebuilt. This could help to address issues like those in Gentoo Bug 167662 and allow easier implementation of support for things like perl-cleaner. Currently, perl-cleaner doesn't detect that vim uses perl and moving from -ithreads to ithreads causes vim to die, so it needs to be manually rebuilt.
Add support for portage to understand which version of a particular app is the "active" version that it was built against, and record this information in /var/db/pkg. This can help to implement perl-cleaner-like support in Portage.
Funtoo Features/Changes
Note
Many of these features have been merged into Gentoo's upstream Portage.
In Funtoo stable/current Portage
- emerge --sync from git
- If a git-based Portage tree is already in place, emerge --sync will run "git pull" to update the underlying Portage tree. If one is not in place, the contents of the SYNC variable will be used as the remote URI from which to clone a git tree (2.2). In addition, SYNC_USER and SYNC_UMASK (defaulting to root and 022) can be used to define the user account to use for cloning/syncing, as well as the umask to use. (2.2).
- Sed Wrapper Symlink and PATH fix
- The Funtoo version of Portage has replaced the BSD-only sed wrapper with a symlink. This will eventually be deprecated. The sed wrapper was a way to provide BSD systems with a "sed" command that could be used inside ebuilds that worked similarly to GNU sed. A PATH fix has been applied so that /bin/sed will be detected first anyway.
- thin-manifest
- Funtoo's Portage supports a special mode of operation where Manifests only contain digests for distfiles and not for files in the Portage tree. This is to eliminate redundant digests since git already provides SHA1 digests. This feature, previously called "mini-manifest", has been moved to a repo-specific option so you do not needed anymore in your Package:Portage (Funtoo)/etc/portage/make.conf. (note: this has now been done, as "thin-manifest" functionality has been integrated into recent versions of Portage, and is being beta tested in Funtoo). Funtoo provides a special "thin-manifest" tree that is smaller than the full-size Portage tree, and is intended to be used instead of the mini-manifest feature.
- preserve bindist through USE filtering
- Normally, anything not in an ebuild's IUSE is stripped from the USE passed to ebuild.sh. This patch allows "bindist" to not be stripped, so it can be used as a means to disable pre-merge sanity checks that may exist in pkg_setup() and pkg_pretend() but will not otherwise affect the resultant build. If "bindist" will affect some functionality in the package, then it should be added to an ebuild's IUSE. This patch allows pkg_setup() and pkg_pretend() to look for "bindist", which indicates that the ebuild is being built for release, typically in an automated fashion, and thus runtime sanity checks that might otherwise run can be optionally skipped. This check is used by the udev-160-r1.ebuild to see if we should fail if we are merging udev on a system where the kernel will not support it. In Metro, this is not a big deal, but on a real production system, merging the udev on an incompatible system will render the kernel inoperable.
- safetydance FEATURE
- A new FEATURE setting is used by Funtoo's udev ebuild called "safetydance" which can be used to manually bypass sanity checks. This is an alternative to the "bindist" approach above. udev-160 in Funtoo Linux supports both approaches and Metro sets "safetydance" by default.
- GLEP 55 removal
- Some code to support GLEP 55 has been removed.
- new metadata format (experimental)
- Some tweaks to ebuild.sh have been made so that it is easier to support new metadata formats in the future.
- xz-utils auto-dependency
- There are several ebuilds in the Gentoo Portage repository that use .xz files but do not explicitly depend on xz-utils. A workaround has been added to ebuild.sh to add this dependency to metadata automatically if a .xz file exists in SRC_URI. This change is not yet in the official Portage sources but is being used on the Funtoo side when generating our git-based Portage trees.
In current development version (2.3.8)
- emerge-webrsync removed
- Gentoo Portage supports already tree syncing method via downloading a .tar.bz2 file containing all the ebuilds. Funtoo supports git syncing only, so the relevant code is removed.
- SYNC_UMASK, SYNC_USER support
- SYNC_USER and SYNC_UMASK can be used to define the user account to use for cloning/syncing, as well as the umask to use.
- pwconv & grpconv are run after emerge
- Portage runs pwconv & grpconv post-emerge to ensure /etc/shadow and /etc/gshadow are valid.
- preserve bindist through USE filtering
- Normally, anything not in an ebuild's IUSE is stripped from the USE passed to ebuild.sh. This patch allows "bindist" to not be stripped, so it can be used as a means to disable pre-merge sanity checks that may exist in pkg_setup() and pkg_pretend() but will not otherwise affect the resultant build. If "bindist" will affect some functionality in the package, then it should be added to an ebuild's IUSE. This patch allows pkg_setup() and pkg_pretend() to look for "bindist", which indicates that the ebuild is being built for release, typically in an automated fashion, and thus runtime sanity checks that might otherwise run can be optionally skipped. This check is used by the udev-160-r1.ebuild to see if we should fail if we are merging udev on a system where the kernel will not support it. In Metro, this is not a big deal, but on a real production system, merging the udev on an incompatible system will render the kernel inoperable.
- Dynamic SLOT support re-enabled
- The ebuilds are allowed to change their SLOT value during build.