|Description||To bring out the virtues of Gentoo on different operating systems, the Gentoo Prefix project develops and maintains a way of installing Gentoo systems in a non-standard location, designated by a "prefix".|
Last elected: 2019-05-04
(and inherited member(s))
To bring out the virtues of Gentoo Linux on different operating systems, the Gentoo Prefix project develops and maintains a way of installing Gentoo systems in a non-standard location, designated by a "prefix".
Usually, Gentoo Linux's package manager (Portage) installs in the root of the filesystem hierarchy known as /. On systems other than Gentoo Linux, this usually results in problems, due to conflicts of software packages, unless the OS is adapted like Gentoo FreeBSD. Instead, Gentoo Prefix installs within an offset, known as a prefix, allowing users to install Gentoo in another location in the filesystem hierarchy, hence avoiding conflicts. Next to this offset, Gentoo Prefix runs unprivileged, meaning no root user or rights are required to use it.
By using an offset (the "prefix" location), it is possible for many "alternative" user groups to benefit from a large part of the packages in the Gentoo ebuild repository. Currently users of the following systems successfully run Gentoo Prefix: macOS on PowerPC and Intel, Linux on x86, x86_64 and arm, Solaris 11 on Sparc, Sparc/64, x86 and x86_64. Other platforms have been successfully used in the past.
Today, there up to 3 variants of Prefix:
1. RAP as in "RAP ain't Prefix" (
For Android and Linux, using host kernel but it's own glibc. This is most similar to Gentoo Linux and does neither need the prefix-overlay nor baselayout-prefix once bootstrapped.
2. Prefix Guest (
The original Prefix as invented, using (POSIX) host libc+kernel. This is the only option for non-Linux, such as macOS (Darwin) and Solaris (SunOS) hosts.
3. Prefix Stack (
USE="prefix prefix-guest prefix-stack")
Use build environment (bash, python, portage, compiler, etc) from some base Prefix (traditionally Prefix Guest on Cygwin) to build packages for platforms (traditionally Win32 using MSVC toolchain) that would not allow for a native portage – but without the whole cross-compilation pain, because Cygwin can very well execute native Win32 binaries.
To get a prefixed Portage installed on your system, you need to go through a few steps we call bootstrapping. Note that, for systems where bash is missing, you need to bootstrap it first with the bootstrap-bash.sh script.
To ease the setup of a prefixed Portage installation, the Gentoo Prefix project provides a script called bootstrap-prefix.sh. This script is a sort of kickstart in the bootstrap process, automating downloading the Portage tree, installing Portage and the necessary temporary helper applications. In addition, it tries to setup a profile and prepares those settings that it can deduce automatically.
The following guides give a detailed description on how to install a Gentoo Prefix system:
- General bootstrap process: for all systems and is recommended for general use.
- Manual bootstrap process: legacy document meant for power-users and not recommended for general use.
Special notes for Microsoft Windows
Gentoo Prefix can be bootstrapped on Cygwin (64-bit). As Microsoft has discontinued the Interix system, we had no option than to follow that decision, even if the outdated Interix installers still might work.
With little restrictions and additional setup, Windows users can install Gentoo Prefix in Cygwin using the General bootstrap process. The documentation and ISO images for the Interix port of Gentoo Prefix on our mirrors still applies to Windows XP and Server 2003.
To keep track of the supported platforms, the following matrix is maintained. It also provides feedback on which developer is maintaining the platform or has direct access to such systems.
|Fabian Groffen (grobian)||Benda Xu (heroxbd)||Guilherme Amadio (amadio)||other||support|
|x||actively maintained by developer|
|o||accessible to developer|
|a||actively maintained by a user/contributor|
|e||experimental effort by user/contributor|
Tested Prefix Installations
A community-maintained table is available here.
Resources offered by the prefix project include:
- Technical documentation - How Gentoo Prefix works, and what changes are necessary to get ebuilds working.
- Use cases - An article with a global overview of Gentoo Prefix, including use cases examplifying who could benefit from a Prefix installation.
- FAQ - Frequently Asked Questions about the Gentoo Prefix project.
- Gentoo On Unrooted Android - Gentoo Prefix on Android
- Open bugs for Component PREFIX
- Open bugs assigned to email@example.com
Hall of Fame
Over time, developers come and go again. Some mysteriously disappear, others loose interest and decide to leave. For all past contributors we would like to express our gratitude towards them for helping the Prefix project to become what it is today.
|Past Prefix developers||Contributions|
|ferringb||Initial Portage developer to start the Prefix branch.|
|kito||First prototypes of Prefix using a tree, Mac OS X installer, many first time engineering and development tasks.|
|exg||Prefix Portage maintainer.|
|genstef||Import of gtk+, qt4 and X11 applications for Mac OS X.|
|pipping||Many package additions for Perl, Python, Ruby and Java, lots of Mac OS X targeted fixes and features, pioneer for Darwin9 (Leopard 10.5) support.|
|drizzt||Mostly reviving Solaris 9 support, by fixing packages in the tree.|
|Christian Faulhammer (fauli)||Gave FreeBSD 8 support a boost, some Interix testing.|
|Markus Duft (mduft)||Gentoo Prefix on Interix and Windows.|
|Jeremy Olexa (darkside)||Lots of support for various arches, merges to gx86, user support.|
|redlizard||Initiated Prefix/libc, early works of the RAP (RAP Aint Prefix) project.|
|Michael Haubenwallner (haubi)||Initiator of Prefix Portage, long standing guardian of AIX, HPUX and Solaris platforms|
This page is based on a document formerly found on our main website gentoo.org.
The following people contributed to the original document: Fabian Groffen (grobian)
They are listed here because wiki history does not allow for any external attribution. If you edit the wiki article, please do not add yourself here; your contributions are recorded on each article's associated history page.