Handbook:Parts/Portage/Tools/es

dispatch-conf
es una herramienta diseñada para combinar los archivos. Los archivos son generados por Portage cuando intenta sobreescribir un archivo en un directorio protegido por la variable CONFIG_PROTECT.

With, users are able to merge updates to their configuration files while keeping track of all changes. stores the differences between the configuration files as patches or by using the RCS revision system. This means that if someone makes a mistake when updating a config file, the administrator can revert the file to the previous version at any time.

When using, users can ask to keep the configuration file as-is, use the new configuration file, edit the current one or merge the changes interactively. also has some nice additional features:


 * Automatically merge configuration file updates that only contain updates to comments
 * Automatically merge configuration files which only differ in the amount of whitespace

Edit first and create the directory referenced by the archive-dir variable. Then, execute :

When running, each changed config file will pass the revue one at a time. Press to update (replace) the current config file with the new one and continue to the next file. Press to zap (delete) the new config file and continue to the next file. Once all config files have been taken care of, will exit. At any time, can be used to exit the application as well.

Para más información, consulte la página man de dispatch-conf. Allí se detalla como combinar interactivamente los de configuración actuales y los nuevos, editar nuevos archivos de configuración, comprobar las diferencias entre archivos y mucho más.

etc-update
Another tool to merge configuration files is. It's not as simple to use as, nor as featureful, but it does provide an interactive merging setup and can also auto-merge trivial changes.

However, unlike, does not preserve the old versions of the config files. Once a file is updated, the old version is gone forever! So be very careful, as using is significantly less safe than using  in that regard.

Después de combinar los cambios sencillos, se presentará una lista con los ficheros protegidos que tienen una actualización pendiente. Al final se muestran las opciones posibles:

With -1, will exit and discontinue any other changes. With -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.

Como ejemplo, seleccionamos el fichero de configuración :

The differences between the two files are shown. If the updated configuration file can be used without problems, enter. If the updated configuration file isn't necessary, or doesn't provide any new or useful information, enter. If the current configuration file has to be interactively updated, enter.

Por ahora, no tiene sentido profundizar más sobre la actualización interactiva. Para completarlo, listaremos los comandos que están disponibles durante la combinación interactiva de ambos ficheros. Son mostradas dos líneas (la original, y la nueva propuesta) y un punto indicativo en el cual puede introducir uno de los comandos siguientes:

After having finished updating the important configuration files, users can then automatically update all the other configuration files. will exit if it doesn't find any more updateable configuration files.

quickpkg
With users can create archives of the packages that are already merged on the system. These archives can be used as prebuilt packages. Running is straightforward: just add the names of the packages to archive.

Por ejemplo, para archivar curl, orage y procps:

Los paquetes precompilados se almacenarán en $PKGDIR (por defecto ). Los paquetes serán ubicados en.