Aggiornare Gentoo! dicembre 14, 2007
Inviato da synthesis in : Informatica, Linux, Tecnologia , trackback
Spesso capita che gli utenti alle prime armi si trovino in difficoltà quando devono aggiornare la loro Gentoo.
Voglio qui segnalare alcune linee guida da seguire, che per me sono state utilissime.
Dopo i comandi riporto la spegazione tratta dal manuale.
Innanzitutto il sistema deve essere sincronizzato con l’albero di portage:
localhost ~ # emerge --sync
Initiates a portage tree update with one of the rsync.gentoo.org mirrors. Note that any changes you have made to the portage tree will be erased. Except for special circumstances, this uses rsync to do the update.
Poi possiamo passare all’aggiornamento vero e proprio del sistema:
localhost ~ # emerge -uDav world
(-u) Updates packages to the best version available, which may not always be the highest version number due to masking for testing and evelopment. This will also update direct dependencies which may
not be what you want. Package atoms specified on the command line are greedy, meaning that unspecific atoms may match multiple installed versions of slotted packages.
(-D) This flag forces emerge to consider the entire dependency tree of packages, instead of checking only the immediate dependencies of the packages. As an example, this catches updates in libraries that are not directly listed in the dependencies of a package. Also see –with-bdeps for behavior with respect to build time dependencies that are not strictly required.
(-a) Before performing the action, display what will take place (server info for –sync, –pretend output for merge, and so forth), then ask whether to proceed with the action or abort. Using –ask is more efficient than using –pretend and then executing the same command without –pretend, as dependencies will only need to be calculated once.
(-v) Tell emerge to run in verbose mode. Currently this flag causes emerge to print out GNU info errors, if any, and to show the USE flags that will be used for each package when pretending.
Come alternativa si potrebbe anche aggiungere il flag –newuse (-N), che specifica di aggiornare il sistema secondo le nuove flags impostate, e aggiornare i pacchetti che non hanno moficato la versione, ma anche solo la use list.
Dopo un tempo che varia dalla velocità della vostra cpu e dalla quantità di pacchetti da aggiornare, siete pronti per lanciare altri due comandi che servono a fare pulizia dei pacchetti inutili e a controllare l’integrità del sistema:
localhost ~ # emerge -av --depclean
–depclean Cleans the system by removing packages that are not associated with explicitly merged packages. Depclean works by creating the full dependency tree from the system list and the world file, then com paring it to installed packages. Packages installed, but not associated with an explicit merge are listed as candidates for unmerging. Inexperienced users are advised to use –pretend with this option in order to see a preview of which packages will be uninstalled.
localhost ~ # revdep-rebuild -av
revdep-rebuild scans libraries and binaries for missing shared library dependencies and fixes them by re-emerging those broken binaries and shared libraries. It is useful when an upgraded package breaks other software packages that are dependent upon the upgraded package.
Spero cheil mini-howto sia stato utile, scrivete commenti se qualcosa non vi è chiaro!
synthesis
Commenti»
no comments yet - be the first?