Repositorio de ebuilds
emerge — configuration — ebuild repository — dispatch-conf
world file — USE flags — ebuilds — profiles
upgrades — using testing packages — binary packages
tools — gentoolkit — eselect
Portage FAQ — cheat sheet — FAQ
all articles
Un repositorio de ebuilds coloquialmente un recubrimiento (Overlay), es una estructura de directorios y ficheros utilizados para añadir y extender paquetes de software en un sistema basado en Gentoo. Los repositorios de ebuilds pueden contener ebuilds que se ajusten a una o más APIs de ebuild. Los respositorios de ebuild contienen ebuilds, eclasses y otros tipos de ficheros descriptivos de metadatos. Estos ficheros informan al gestor de paquete del software que está disponible para su instalación. Un repositorio de ebuilds debe respetar uno o más de las APIs Ebuild tal y como se describe en la Especificación del Gestor de Paquetes de Gentoo.
The Gentoo ebuild repository is Gentoo Linux's primary and official ebuild repository - it contains all the information needed to build and install every package that makes up Gentoo. Additional ebuild repositories, such as GURU, can be configured with Portage, to provide even more packages.
Portage will install the latest available version of a package from any configured ebuild repository, by default. If the latest available version is provided by several ebuild repositories, it will be chosen according to a set order of priority - hence the colloquial name overlay.
Los administradores de los sistemas Gentoo pueden añadir repositorios de ebuilds adicionales utilizando diferentes herramientas y métodos que se describen más abajo.
The Gentoo ebuild repository
El repositorio inicial de un sistema Gentoo se llama el repositorio de ebuilds de Gentoo. Este término a veces se abrevia como Gentoo repo, ::gentoo, gentoo.git, o también simplemente "repo". Históricamente se conocía entre la comunidad de Gento como el árbol de Portage, el árbol rsync, o también simplemente "el árbol". El repositorio de ebuilds de Gentoo cotiene ebuilds que son mantenidas por los desarrolladores oficiales de Gentoo y también por miembros de la comunidad (a través del proyecto Proxy Maintainers).
The Gentoo ebuild repository contains ebuild files that tell Portage how to build and install each package. The ebuilds come with metadata, dependency information, and everything else needed to get a package in working order.
The metadata provides the package's name, version, where to get sources from, available USE flags, license, website etc. Dependency information in ebuilds allows Portage to pull in any other packages required to build and run a package that is to be installed - no more, no less. Dependencies are very granular in Gentoo, they will even vary depending on what use flags are selected, for ultimate selectivity. Perhaps most importantly, ebuilds contain the information required to configure, build (compile), install, and test each package - usually from a project's own source code.
In addition to ebuilds, the Gentoo ebuild repository contains the official profiles, which define the default state of USE flags, default values for most variables found in /etc/portage/make.conf, the set of system packages, etc.
The Gentoo ebuild repository is also the place where news items are posted, which is why any new news items will be highlighted after a Gentoo ebuild repository synchronization.
The Gentoo ebuild repository, and it's ebuilds, are maintained by the Gentoo developers and other members of the community.
The Gentoo ebuild repository will sometimes be called by shorter, or even colloquial, names, such as the Gentoo repository, the Gentoo repo, ::gentoo, gentoo.git, or occasionally just the "repo". It is also historically and commonly known within the Gentoo community as the Portage tree, rsync tree, or sometimes just "the tree".
GURU is an official ebuild repository maintained collaboratively by Gentoo users, with a little help from a few Gentoo developers. It is complimentary to the Gentoo ebuild repository, and the maintainers strive to keep up a reasonable level of quality for the packages provided. There is also a list of public ebuild repositories registered on repos.gentoo.org.
Where do ebuild repositories come from?
Because an ebuild repository is simply a structure of files and directories, a new ebuild repository can be made available to Portage simply by copying those files and directories to a location known to Portage. The ebuild repositories and their files are usually under /var/db/repos/, but the location of repositories configured for Portage is specified in /etc/portage/repos.conf. Ebuild repositories can be configured on any accessible filesystem however, even on an nfs or SSHFS filesystem - allowing them to be stored on a network or Internet server.
As previously discussed, the Gentoo ebuild repository is hosted on gitweb.gentoo.org. That server also hosts other ebuild repositories.
In practice, any additional ebuild repositories usually aren't just copied to a directory by hand and configured for Portage (meaning added to /etc/portage/repos.conf). Generally, new repositories are made available by third parties, and once configured for Portage, are synchronized by Portage. Synchronization mirrors all the files from a remote location to a locally available filesystem, as configured.
Because ebuild repositories are just file-structures, many methods can be used to synchronize them, and Portage offers several possibilities. Rsync is the default synchronization method, git is also popular. The synchronization method is specified in /etc/portage/repos.conf when configuring a repository, along with the information needed to retrieve it.
Herramientas disponibles
eselect repository mantiene las entradas /etc/portage/repos.conf para que Portage pueda acceder y sincronizar. Lea el artículo Eselect/Repository para más detalles.
Ebuild repositories can always be configured manually, by editing /etc/portage/repos.conf.
While the Gentoo ebuild repository is either written or reviewed by Gentoo developers, and the GURU repository has some developer oversight, that is not always the case for other ebuild repositories. It is possible that some ebuild repositories might contain vulnerable, badly broken or, theoretically, even malicious software.
New ebuild repositories for use with Portage can also be created by the user.
Se puede obtener la lista de repositorio de ebuilds y sus prioridades consultando la salida de las siguientes ordenes (Buscar la palabra "Repositories"):
user $emerge --info --verboseuser $portageq repos_config /Installing packages from other repositories
Packages from repositories other than the Gentoo ebuild repository can be installed with the emerge command, just as usual.
For example, once the GURU repository is added, to install the x11-misc/xbanish package from that repository:
root #emerge --ask x11-misc/xbanishThese are the packages that would be merged, in order: Calculating dependencies... done! Dependency resolution took 2.96 s. [ebuild R #] x11-misc/xbanish-1.7::guru 0 KiB Total: 1 package (1 reinstall), Size of downloads: 0 KiB
Note that the repository is not specified in the command. The "::guru" appended to the package atom in the output shows what repository the package will be installed from. This works because the x11-misc/xbanish package is present in the GURU repository, but not in the Gentoo repository.
If multiple versions of the same package are available from two or more different ebuild repositories, Portage will install the most recent version.
{{{1}}}
Cada repositorio de ebuilds tiene una prioridad única para el gestor de paquetes. Esto asegura que en el caso de que una versión en particular se encuentre en varios repositorios de ebuilds, la resolución de la misma no es ambigua. Los ebuilds de los repositorios con números de prioridad más altos (por ejemplo 60) tendrán preferencia sobre los ebuilds de repositorios con menores prioridades (por ejemplo 50).
It is possible to instruct Portage to install a package from a specific ebuild repository with the :: version specifier (can be used for different emerge instructions, e.g. uninstalling a package through --depclean):
root #emerge --ask category/atom::repository-nameSee the repository management section to see how to list repositories configured for portage with their respective priorities.
Repository synchronization
Ebuild repositories should be synchronized, so that the local mirrors will reflect a recent state of the repositories. This is necessary to be able to keep the system up to date, and install current software.
Regularly synchronizing with the Gentoo repository and updating the system in this way is important, to ensure that all the latest security updates are installed, and that the local system does not get too out of sync with the Gentoo repository, as this can make upgrades complicated if things have moved too far on in the repository.
Synchronize and update between daily or weekly to keep a Gentoo Linux installation running smoothly with the latest security updates. Waiting more than a few weeks to update may make things a little more complicated when the update is attempted. Please don't synchronize more than once daily, to avoid strain on the servers.
If local repositories are not very up to date, synchronize the repositories and update the system, before installing packages.
Lea el artículo Sync (Portage project) y man 1 emaint.
user $emaint --helpusage: usage: emaint [options] COMMAND
<nowiki/>
The emaint program provides an interface to system health checks
and maintenance. See the emaint(1) man page for additional
information about the following commands:
<nowiki/>
Commands:
all Perform all supported commands
binhost Scan and generate metadata indexes for binary packages.
cleanconfmem Check and clean the config tracker list for uninstalled packages.
cleanresume Discard emerge --resume merge lists
logs Check and clean old logs in the PORTAGE_LOGDIR.
merges Scan for failed merges and fix them.
movebin Perform package move updates for binary packages
moveinst Perform package move updates for installed and binary packages.
sync Check repos.conf settings and sync repositories.
world Check and fix problems in the world file.
<nowiki/>
optional arguments:
-h, --help show this help message and exit
-c, --check Check for problems (a default option for most modules)
-f, --fix Attempt to fix problems (a default option for most modules)
--version show program's version number and exit
-C, --clean Cleans out logs more than 7 days old (cleanlogs only) module-options: -t, -p
-t NUM, --time NUM (cleanlogs only): -t, --time Delete logs older than NUM of days
-p, --pretend (cleanlogs only): -p, --pretend Output logs that would be deleted
-P, --purge Removes the list of previously failed merges. WARNING: Only use this option if you plan on manually fixing them or do not want them re-installed.
-y, --yes (merges submodule only): Do not prompt for emerge invocations
-r REPO, --repo REPO (sync module only): -r, --repo Sync the specified repo
-A, --allrepos (sync module only): -A, --allrepos Sync all repos that have a sync-url defined
-a, --auto (sync module only): -a, --auto Sync auto-sync enabled repos only
--sync-submodule {glsa,news,profiles}
(sync module only): Restrict sync to the specified submodule(s)
To sync all repositories for which auto-sync=true is set, run emaint sync with the --auto switch (-a for short). This is usually the command that should be run regularly, before system updates and package installation (and is equivalent to using the old emerge --sync command):
root #emaint sync --autoTo sync the foo repository (irrespective of the foo auto-sync setting):
root #emaint sync --repo fooTo sync all repositories with a valid sync-type and sync-url defined (ignoring auto-sync settings):
root #emaint sync --allreposFor any repositories that should not be synced when running emaint sync --auto,
auto-sync = no must be set in the appropriate file in /etc/portage/repos.conf, due to the default being auto-sync = true.eix-sync es un envoltorio para emerge --sync (que de hecho lanza emaint sync --auto) seguido de eix-update. Para más detalles, leer el artículo sobre Eix y man 1 eix.
The emerge-webrsync tool can be used to download and install the daily Gentoo Repository rsync snapshot, to help with firewall restrictions, or to speed up the first synchronization, for example.
See man emaint for information on how to use the portage synchronization commands. See the Portage project sync article about migrating to the new modular sync system from Portage version 2.2.16, it contains important information, notably for users of eix-sync, esync -l, and emerge --sync .
Buenas prácticas
Generación de cache
Cuando se instalan repositorios de ebuilds muy voluminosos, a Portage le puede llevar mucho tiempo realizar operaciones como la resolución de dependencias. Esto es debido a que los repositorios de ebuilds no suelen contener una caché para los metadatos.
Generar una caché local para metadatos lanzando emerge --regen después de sincronizar los repositorios de ebuilds:
root #emaint sync --allrepos
root #( ulimit -n 4096 && emerge --regen )Hay que ser cuidadoso ya que emerge --regen lleva bastante tiempo y no se recomienda a los usuarios de rsync ya que rsync actualiza la caché usando caché del servidor (la mayoría de los usuarios de portage son usuarios rsync). Estos usuarios deberían simplemente lanzar emerge --sync (o eix-sync) para regenerar la caché. Probablemente solo los usuarios de repositorios de ebuilds muy voluminosos deberían correr emerge --regen.
Enmascaramiento de repositorios de ebuild instalados pero inseguros
Cuando se utilizan repositorios de ebuilds con muchos paquetes o se cree que contienen código de baja o desconocida calidad, es una buena práctica enmascarar de forma dura (hard mask) todo el repositorio de ebuilds y únicamente aceptar determinados ebuilds basándose en una estrategia caso por caso. Por ejemplo, para un recubrimiento llamado "repository-foobar":
/etc/portage/package.maskEnmascarar todos los paquetes de un repositorio de ebuilds*/*::repository-foobar
A continuación añadir el paquete o paquetes específicos desde el recubrimiento repository-foobar de modo que estén disponibles y visibles para la instalación de Portage:
/etc/portage/package.unmaskDesenmascarar un paquete específico en un repositorio de ebuildsfoo-category/bar::nombre-del-repositorio
Después del desenmascaramiento de arriba, el paquete llamado "foo-category/bar" debería estar disponible y ningún otro paquete del recubrimiento repository-foobar estaría disponible, lo que es así por diseño.
Véase también
- Proyecto de Overlays. El proyecto oficial de Gentoo de soporte de repositorios de ebuilds.
- Guía de Overlays (Proyecto Overlays). Una guía de usuario escrita por el proyecto Overlay.
- Guía del desarrollador de Overlays en Gentoo. Este documento se conserva únicamente por razones históricas. La guía actual se mantiene en Project:Overlays/Overlays guide.
- Definiendo un repositorio personalizado. La sección del manual de Gentoo