Difference between pages "Package:Portage (Funtoo)" and "Subarches"

(Difference between pages)
m (Drobbins moved page Portage (Funtoo) to Package:Portage (Funtoo))
 
 
Line 1: Line 1:
== Introduction ==
+
{{:Install/Header}}
 +
= Funtoo Linux Sub-Architectures =
 +
__NOTITLE__
 +
This page provides an overview of Funtoo Linux sub-architectures (also called ''subarches'') designed for quick and easy reference. Funtoo Linux provides optimized installation images for all sub-architectures listed below. See the [[Funtoo Linux Installation|Funtoo Linux Installation Guide]] to install Funtoo Linux.
  
Portage is the official package manager of Funtoo Linux. Daniel Robbins maintains a slightly different version from upstream Gentoo Linux, with support for mini-manifests and other features.
+
The cpuid application can be used to help identify your processor and it's microarchitecture.
 +
<console>
 +
sudo emerge cpuid; cpuid | tail -n 1
 +
</console>
  
== Portage Commands ==
+
== 64-bit PC-Compatible ==
  
; [[emerge]]
+
{{TableStart}}
: high-level dependency-based package merge/unmerge tool
+
<tr><th class="warn" colspan="3">64-bit AMD Processors</th></tr>
; [[ebuild]]
+
{{#ask:[[CPU Family::64-bit AMD Processors]]
: lower-level package build tool
+
|?#
 
+
|?Subarch
== Portage Specifications ==
+
|?CFLAGS
 
+
|?Description
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 [http://www.gentoo.org/proj/en/council/ Gentoo Council page].
+
|format=template
 
+
|link=none
The latest PMS specification to be approved by the Gentoo Council is available: [http://distfiles.gentoo.org/distfiles/pms-3.pdf eapi-3-approved-2010-01-18]. The PMS specification is an attempt to codify the inner workings of Portage, and is authored by Ciaran McCreesh and Stephen Bennett as a Gentoo-hosted project.
+
|headers=hide
 
+
|searchlabel=... further results
== Portage Profiles ==
+
|sep=,
 
+
|template=SubarchList
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.
+
}}
 
+
<tr><th class="warn" colspan="3">64-bit Intel Processors</th></tr>
== Portage Variables ==
+
{{#ask:[[CPU Family::64-bit Intel Processors]]
 
+
|?#
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]].
+
|?Subarch
 
+
|?CFLAGS
== Multiple ABI Support ==
+
|?Description
 
+
|format=template
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]].
+
|link=none
 
+
|headers=hide
== Ebuild Functions ==
+
|searchlabel=... further results
 
+
|sep=,
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]].
+
|template=SubarchList
 
+
}}
== Funtoo Portage Development ==
+
<tr><th class="warn" colspan="3">64-bit PC-Compatible (Generic) Processors</th></tr>
 
+
{{#ask:[[CPU Family::64-bit Processors (PC-Compatible, Generic)]]
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.
+
|?#
 
+
|?Subarch
=== TODO ===
+
|?CFLAGS
 
+
|?Description
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 [http://bugs.gentoo.org/167662 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.
+
|format=template
 
+
|link=none
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.
+
|headers=hide
 
+
|searchlabel=... further results
== Funtoo Features/Changes ==
+
|sep=,
 
+
|template=SubarchList
=== Summary ===
+
}}
 
+
{{TableEnd}}
In [https://github.com/funtoo/portage-funtoo/tree/thin-manifest the thin-manifest branch], Funtoo changes have been isolated into the following commits:
+
 
+
<pre>
+
e5a6649e094eb7230aa8f56d97fe303f77b158e9 preserve bindist through use expansion
+
5a092fdae8afbff679350dc5d8818e10ab35fd80 safetydance feature
+
16887ddce712da8b61887f9bce70e19b95e75c25 core funtoo git-sync implementation
+
2c6e2b427a2aa179b61667caf89497818ec34ae2 run pwconv and grpconv after emerge completes to ensure /etc/shadow and /etc/gshadow are valid.
+
ea565da9ab5f54580f66814a17aca39d8e568732 funtoo-specific man page changes
+
c8f130fa4b332d87f2202ddaf0222b89018914d0 Funtoo config file changes. This includes stuff related to rsync as well as /lib/firmware
+
dba5a350e16043a6ff6281ea80fc02c8f56efd4f remove emerge-webrsync -- not supported in funtoo
+
0d9dda7b2b3165b268545e3e8eb44aa8d3c20a57 small ebuild.sh fix to not source any stray directories
+
8500043b3075d26c77a7ec1b8c2745373ca0c3b5 disable warning for use of *, -* in KEYWORDS
+
86ed81605e73b8b6d6b06fc60a9a0bc0c13ee429 protect firmware as well as modules
+
e7b6512e582fbcd9af0eb82c617549b101c8ae97 slashbeast's localpatch feature
+
5af34ad9334310c0926e52d9e1801ee170e12184 simplify path setting in ebuild.sh by using getpath() function
+
42789a70184343008c4cb1fe20bc4398e881d285 remove bin/ebuild-helpers/sed
+
</pre>
+
 
+
These commits do not yet include the unified-path/funtoo-profile 1.0 patches.
+
 
+
=== In Funtoo stable/current Portage ===
+
 
+
;emerge --sync from git
+
:If a git-based Portage tree is already in place, <tt>emerge --sync</tt> 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.
+
 
+
;mini-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 is currently enabled by adding "mini-manifest" to FEATURES in /etc/make.conf but the intention is to eventually move it to a repo-specific option (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 "mini-manifest" tree that is smaller than the full-size Portage tree, and is intended to be used with 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.
+
 
+
[[Category:Projects]]
+
[[Category:Portage]]
+

Revision as of 10:08, December 20, 2014

Funtoo Linux Sub-Architectures

This page provides an overview of Funtoo Linux sub-architectures (also called subarches) designed for quick and easy reference. Funtoo Linux provides optimized installation images for all sub-architectures listed below. See the Funtoo Linux Installation Guide to install Funtoo Linux.

The cpuid application can be used to help identify your processor and it's microarchitecture.

sudo emerge cpuid; cpuid | tail -n 1

64-bit PC-Compatible

64-bit AMD Processors
amd64-bulldozerThe amd64-bulldozer subarch supports the AMD bulldozer microarchitecture CPUs, which were released from late 2011 through the first quarter of 2012 as a replacement for the K10 microarchitecture CPUs.-march=bdver1 -O2 -pipe
amd64-jaguarAMD jaguar microarchitecture debuted in mid-2013 and is targeted at low-power devices, including notebooks, tablets and small form-factor desktops and servers. It is perhaps most well-known for being the microarchitecture used for the Playstation 4 and Xbox One,-march=btver2 -O2 -pipe
amd64-k10The amd64-k10 subarch provides support for the AMD Family 10h processors, which were released in late 2007 as a successor to the AMD K8 series processors.-march=amdfam10 -O2 -pipe
amd64-piledriverThe amd64-piledriver subarch supports the AMD Piledriver microarchitecture produced by AMD from mid-2012 through 2015, which is the successor to the AMD bulldozer microarchitecture.-march=bdver2 -O2 -pipe
amd64-steamrollerThe amd64-steamroller subarch supports the AMD steamroller microarchitecture, produced from early 2014. It is the successor to the AMD Piledriver microarchitecture.-march=bdver3 -O2 -pipe
64-bit Intel Processors
atom_64The atom_64 sub-architecture supports 64-bit capable Intel Atom CPUs.-O2 -fomit-frame-pointer -march=atom -pipe
core2-64The core2_64 subarch supports 64-bit-capable processors based on the Core microarchitecture and all processors of the Penryn microarchitecture. This includes all Intel Core 2 branded processors, some Celeron, some Pentium and some Xeon branded processors.-march=core2 -O2 -pipe
corei7The corei7 subarch supports the Nehalem, Westmere, Sandy_Bridge, Ivy Bridge, and Haswel microarchitecture-based Intel Pentium/Celeron, Intel Core i3, i5, i7 and Xeon Processors.-march=corei7 -O2 -pipe
intel64-haswellThe intel64-haswell subarch specifically supports processors based on Intel's Haswell microarchitecture. Haswell desktop processors are branded as 4th Generation Intel Core i3, Core i5, and Core i7 Processors.-march=core-avx2 -O2 -pipe
64-bit PC-Compatible (Generic) Processors
generic_64The generic_64 subarch is designed to support 64-bit PC-compatible CPUs, such as the AMD K8-series processors, which were introduced in late 2003.-mtune=generic -O2 -pipe