You probably all know Gentoo Linux as your favourite source-based distribution. Did you know that our package manager, Portage, already for years also has support for binary packages, and that source- and binary-based package installations can be freely mixed?
你们可能都知道Gentoo Linux是你最喜欢的基于源代码的发行版。你知道吗，我们的软件包管理器Portage，已经支持二进制软件包了，并且基于源代码和二进制的软件包安装可以自由混合使用？

To speed up working with slow hardware and for overall convenience, we’re now also offering binary packages for download and direct installation! For most architectures, this is limited to the core system and weekly updates - not so for amd64 and arm64 however. There we’ve got a stunning >20 GByte of packages on our mirrors, from LibreOffice to KDE Plasma and from Gnome to Docker. Gentoo stable, updated daily. Enjoy! And read on for more details!
为了加快使用慢速硬件的速度并实现整体便利，我们现在还提供二进制包供下载和直接安装！对于大多数架构，这仅限于核心系统和每周更新，但对于 amd64 和 arm64 则不然。我们的镜像上有惊人的 >20 GB 的软件包，从 LibreOffice 到 KDE Plasma，从 Gnome 到 Docker。Gentoo稳定版，每日更新。享受！请继续阅读以获取更多详细信息！

Questions & Answers 问题和答案

How can I set up my existing Gentoo installation to use these packages?
我该如何设置我现有的Gentoo安装来使用这些软件包？

Quick setup instructions for the most common cases can be found in our wiki. In short, you need to create a configuration file in /etc/portage/binrepos.conf/.
最常见情况的快速设置说明可以在我们的 wiki 中找到。简而言之，您需要在 中 /etc/portage/binrepos.conf/ 创建一个配置文件。

In addition, we have a rather neat binary package guide on our Wiki that goes into much more detail.
此外，我们的 Wiki 上有一个相当简洁的二进制包指南，其中有更详细的介绍。

What do I have to do with a new stage / new installation?
我与新阶段/新安装有什么关系？

New stages already contain the suitable /etc/portage/binrepos.conf/gentoobinhost.conf. You are good to go from the start, although you may want to replace the src-uri setting in there with an URI pointing to the corresponding directory on a local mirror.
新阶段已经包含合适的 /etc/portage/binrepos.conf/gentoobinhost.conf .您可以从一开始就开始，尽管您可能希望将其中 src-uri 的设置替换为指向本地镜像上相应目录的 URI。

$ emerge -uDNavg @world

What compile settings, use flags, … do the ‘‘normal’’ amd64 packages use?
什么编译设置，使用标志，...''normal'' amd64 软件包是否使用？

The binary packages under amd64/binpackages/17.1/x86-64 are compiled using CFLAGS="-march=x86-64 -mtune=generic -O2 -pipe" and will work with any amd64 / x86-64 machine.
下面的 amd64/binpackages/17.1/x86-64 二进制包是使用 CFLAGS="-march=x86-64 -mtune=generic -O2 -pipe" 任何 amd64 / x86-64 机器编译的，并且可以与任何 amd64 / x86-64 机器一起使用。

The available useflag settings and versions correspond to the stable 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 should provide fairly large coverage.
可用的 useflag 设置和版本对应于 amd64/17.1/nomultilib （即 openrc）、 amd64/17.1/desktop/plasma/systemd 和 amd64/17.1/desktop/gnome/systemd profiles 的稳定包。这应该提供相当大的覆盖范围。

What compile settings, use flags, … do the ‘‘normal’’ arm64 packages use?
什么编译设置，使用标志，...是否使用“正常”的 ARM64 包？

The binary packages under arm64/binpackages/17.0/arm64 are compiled using CFLAGS="-O2 -pipe" and will work with any arm64 / AArch64 machine.
下面的 arm64/binpackages/17.0/arm64 二进制包是使用 CFLAGS="-O2 -pipe" 任何 arm64 / AArch64 机器编译的，并且可以与任何 arm64 / AArch64 机器一起使用。

The available useflag settings and versions correspond to the stable packages of the arm64/17.0 (i.e., openrc), arm64/17.0/desktop/plasma/systemd, and arm64/17.0/desktop/gnome/systemd profiles.
可用的 useflag 设置和版本对应于 arm64/17.0 （即 openrc）、 arm64/17.0/desktop/plasma/systemd 和 arm64/17.0/desktop/gnome/systemd profiles 的稳定包。

But hey, that’s not optimized for my CPU!
但是，嘿，这没有针对我的 CPU 进行优化！

Tough luck. You can still compile packages yourself just as before!
运气不好。您仍然可以像以前一样自己编译包！

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

【未完待续，点击下方/Continue Read more, please click the Read More button】