Gentoo goes Binary! – Gentoo Linux

2023-12-29 06:12:59

You in all probability all know Gentoo Linux as your favorite source-based distribution.
Do you know that our package deal supervisor, Portage, already for years additionally has help for binary
packages, and that source- and binary-based package deal installations could be freely blended?

To hurry up working with gradual {hardware} and for total comfort, we’re now additionally providing
binary packages for obtain and direct set up! For many architectures, that is
restricted to the core system and weekly updates – not so for amd64 and arm64 nonetheless. There we’ve obtained a
gorgeous >20 GByte of packages on our mirrors, from LibreOffice to KDE Plasma and from Gnome to Docker.
Gentoo secure, up to date every day. Get pleasure from! And read
on for more details!

Questions & Solutions

How can I arrange my present Gentoo set up to make use of these packages?

Quick setup instructions for
the commonest circumstances could be present in our wiki. Briefly, you could create a configuration
file in /and so on/portage/binrepos.conf/.

As well as, we’ve got a moderately neat binary package guide on
our Wiki that goes into rather more element.

What do I’ve to do with a brand new stage / new set up?

New phases already comprise the appropriate /and so on/portage/binrepos.conf/gentoobinhost.conf. You might be
good to go from the beginning, though you might wish to exchange the src-uri
setting in there with an URI pointing to the corresponding listing on a
local mirror.

$ emerge -uDNavg @world

What compile settings, use flags, … do the ‘‘regular’’ amd64 packages use?

The binary packages below amd64/binpackages/17.1/x86-64 are compiled utilizing
CFLAGS="-march=x86-64 -mtune=generic -O2 -pipe" and can work with any amd64 / x86-64 machine.

The accessible useflag settings and variations correspond to the secure packages
of the amd64/17.1/nomultilib (i.e., openrc), amd64/17.1/desktop/plasma/systemd,
and amd64/17.1/desktop/gnome/systemd profiles. This could present pretty giant
protection.

What compile settings, use flags, … do the ‘‘regular’’ arm64 packages use?

The binary packages below arm64/binpackages/17.0/arm64 are compiled utilizing
CFLAGS="-O2 -pipe" and can work with any arm64 / AArch64 machine.

The accessible useflag settings and variations correspond to the secure packages
of the arm64/17.0 (i.e., openrc), arm64/17.0/desktop/plasma/systemd,
and arm64/17.0/desktop/gnome/systemd profiles.

However hey, that’s not optimized for my CPU!

Robust luck. You may nonetheless compile packages your self simply as earlier than!

What settings do the packages for different architectures and ABIs use?

The binary package deal internet hosting is wired up with the stage builds. Which
means, for about each stage there’s a binary package deal internet hosting which
covers (solely) the stage contents and settings. There aren’t any additional plans
to broaden protection for now. However hey, this contains the compiler (gcc or
clang) and the entire construct toolchain!

Are the packages cryptographically signed?

Sure, with the same key as the stages.

Are the cryptographic signatures verified earlier than set up?

Sure, with one limitation (within the default setting).

Portage is aware of two binary package deal codecs, XPAK (previous) and GPKG (new). Solely GPKG helps
cryptographic signing. Till just lately, XPAK was the default setting (and it might nonetheless
be the default in your set up since this isn’t modified throughout improve, however solely
at new set up).

The brand new, official Gentoo binary packages are all in GPKG format.
GPKG packages have their signature verified, and if this fails, set up is refused.
To keep away from breaking compatibility with previous binary packages, by default XPAK
packages (which don’t have signatures) can nonetheless be put in nonetheless.

If you wish to require verified signatures (which is one thing we strongly advocate),
set FEATURES="binpkg-request-signature" in make.conf. Then, clearly, you can too
solely use GPKG packages.

I get an error that signatures can’t be verified.

Attempt operating the Gentoo Belief Software getuto as root.

$ getuto

This could arrange the required key ring with the Gentoo Launch Engineering keys for
Portage.

You probably have FEATURES="binpkg-request-signature" enabled in make.conf, then getuto
is named robotically earlier than each binary package deal obtain operation, to ensure
that key updates and revocations are imported.

I’ve made binary packages myself and portage refuses to make use of them now!

Nicely, you discovered the facet impact of FEATURES="binpkg-request-signature".
To your self-made packages you’ll need to arrange a signing key and have that key
trusted by the anchor in /and so on/portage/gnupg.

The binary package guide on
our Wiki can be useful right here.

My obtain is gradual.

Then fairly please use a local mirror
as a substitute of downloading from College of Oregon. You may simply edit the URI
in your /and so on/portage/binrepos.conf. And sure, that’s protected, due to the
cryptographic signature.

My Portage nonetheless needs to compile from supply.

In the event you use useflag combos deviating from the profile default, then
you possibly can’t and received’t use the packages. Portage will fortunately combine and match although
and mix binary packages with domestically compiled ones. Gentoo nonetheless stays
a source-based distribution, and we aren’t aiming for a full binary-only
set up with none compilation in any respect.

Can I exploit the packages on a merged-usr system?

Sure. (If something breaks, then this can be a bug and should be reported.)

Can I exploit the packages with different (older or newer) profile variations?

No. That’s why the src-uri path incorporates, e.g., “17.1”.
When there’s a brand new profile model, we’ll additionally present new, separate package deal directories.

Any plans to supply binary packages of ~amd64 ?

Not but. This might imply a ton of rebuilds… If we provide it in the future, it’ll
be at a separate URI for technical causes.

The recommendation for now could be to stay to secure as a lot as attainable, and domestically
add in package deal.accept_keywords no matter packages from testing you wish to use.
This implies you possibly can nonetheless use a considerable amount of binary packages, and simply
compile the remaining your self.

I’ve discovered an issue, with portage or a particular package deal!

Then please ask for recommendation (on IRC, the boards, or a mailing listing) and/or
file a bug!

Binary package deal help has been examined for a while, however with many extra folks utilizing
it edge circumstances will definitely happen, and high quality bug reviews are at all times appreciated!