Renuncia de responsabilidad:
Este manual ha sido sustituido por una versión más reciente y no tendrá
soporte de aquí en adelante.
[ << ]
[ < ]
[ Inicio ]
[ > ]
[ >> ]
4. Herramientas Adicionales de Portage
etc-update is a tool that aids in merging the
._cfg0000_<name> files. It provides an interactive merging
setup and can also auto-merge trivial changes.
._cfg0000_<name> files are generated by Portage when it wants
to store a file in a directory protected by the CONFIG_PROTECT variable.
Running etc-update is pretty straight-forward:
Listado de Código 1.1: Running etc-update
After merging the straightforward changes, you will be prompted with a list of
protected files that have an update waiting. At the bottom you are greeted by
the possible options:
Listado de Código 1.2: etc-update options
Please select a file to edit by entering the corresponding number.
(-1 to exit) (-3 to auto merge all remaining files)
(-5 to auto-merge AND not use 'mv -i'):
If you enter -1, etc-update will exit without performing any
changes. If you enter -3 or -5, all listed configuration
files will be overwritten with the newer versions. It is therefore very
important to first select the configuration files that should not be
automatically updated. This is simply a matter of entering the number listed to
the left of that configuration file.
As an example, we select the configuration file /etc/pear.conf:
Listado de Código 1.3: Updating a specific configuration file
Beginning of differences between /etc/pear.conf and /etc/._cfg0000_pear.conf
End of differences between /etc/pear.conf and /etc/._cfg0000_pear.conf
1) Replace original with update
2) Delete update, keeping original as is
3) Interactively merge original with update
4) Show differences again
You can now see the differences between the two files. If you believe that the
updated configuration file can be used without problems, enter 1. If you
believe that the updated configuration file isn't necessary, or doesn't provide
any new or useful information, enter 2. If you want to interactively
update your current configuration file, enter 3.
There is no point in further elaborating the interactive merging here. For
completeness sake, we will list the possible commands you can use while you are
interactively merging the two files. You are greeted with two lines (the
original one, and the proposed new one) and a prompt at which you can enter one
of the following commands:
Listado de Código 1.4: Commands available for the interactive merging
ed: Edit then use both versions, each decorated with a header.
eb: Edit then use both versions.
el: Edit then use the left version.
er: Edit then use the right version.
e: Edit a new version.
l: Use the left version.
r: Use the right version.
s: Silently include common lines.
v: Verbosely include common lines.
When you have finished updating the important configuration files, you can now
automatically update all the other configuration files. etc-update will
exit if it doesn't find any more updateable configuration files.
Using dispatch-conf you are able to merge updates to your configuration
files while keeping track of all changes. dispatch-conf stores the
differences between the configuration files as patches or by using the RCS
Like etc-update, you can ask to keep the configuration file as-is, use
the new configuration file, edit the current one or merge the changes
interactively. However, dispatch-conf also has some nice additional
Automatically merge configuration file updates that only contain updates to
Automatically merge configuration files which only differ in the amount of
Make certain you edit /etc/dispatch-conf.conf first and create the
directory referenced by the archive-dir variable.
For more information, check out the dispatch-conf man page:
Listado de Código 2.1: Reading the dispatch-conf man page
$ man dispatch-conf
With quickpkg you can create archives of the packages that are already
merged on your system. These archives can be used as prebuilt packages. Running
quickpkg is straightforward: just add the names of the packages you want
For instance, to archive curl, arts and procps:
Listado de Código 3.1: Example quickpkg usage
# quickpkg curl arts procps
The prebuilt packages will be stored in /usr/portage/packages/All.
Symbolic links pointing to these packages are placed in
[ << ]
[ < ]
[ Inicio ]
[ > ]
[ >> ]
El contenido de este documento, a no ser que se especifique
expresamente, está registrado bajo los términos de la licencia
CC-BY-SA-2.5. Se aplican las
Utilización del logotipo y nombre de Gentoo.