Handbook:Parts/Portage/Tools/it

dispatch-conf
è uno strumento che aiuta ad unire i file. I file sono generati da Portage quando vuole sovrascrivere un file in una cartella protetta tramite variabile CONFIG_PROTECT.

Con, gli utenti sono in grado di unire gli aggiornamenti ai loro file configurazione mentre si tiene traccia di tutti i cambiamenti. conserva le differenze tra i file configurazione servendosi di aggiustamenti (patch) o utilizzando il sistema di revisione RCS. Ciò significa che se qualcuno commette un errore durante l'aggiornamento di un file di configurazione, l'amministratore può ripristinare il file alla versione precedente in qualsiasi momento.

Quando si usa, gli utenti possono chiedere di tenere i file configurazione così come sono, usare il nuovo file di configurazione, modificare quello attuale o fondere i cambiamenti in modo interattivo. possiede anche alcune interessanti funzionalità aggiuntive:


 * Fonde automaticamente gli aggiornamenti ai file configurazione che contengono solo aggiornamenti ai commenti.
 * Fonde automaticamente i file configurazione che differiscono solo per la quantità di spazi bianchi.

Modificare prima e creare la cartella a cui fa riferimento la variabile archive-dir. Poi eseguire :

When running, each changed config file will be reviewed 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. The key will instruct  to skip to the next file. This can be done to delay a merge until a future time. Once all config files have been taken care of, will exit. At any time, can be used to exit the application as well.

For more information, check out the dispatch-conf man page. It describes how to interactively merge current and new config files, edit new config files, examine differences between files, and more.

etc-update
Another tool to merge configuration files is. It is not as simple to use as, nor as fully featured, 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. Be very careful, as using is significantly less safe than using  when desiring to keep old configuration files.

After merging the straightforward changes, a list of protected files will be provided that have an update waiting. At the bottom the possible options are shown:

When entering,  will exit and discontinue any other changes. With  or , 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 :

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.

There is no point in further elaborating the interactive merging here. For completeness sake, we will list the possible commands that can be used while interactively merging the two files. Users are greeted with two lines (the original one, and the proposed new one) and a prompt at which the user can enter one of the following commands:

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.

For instance, to archive curl, orage, and procps:

The prebuilt packages will be stored in $PKGDIR ( by default). These packages are placed in.