Difference between revisions of "Gentoo: System update"

Revision as of 15:12, 9 May 2017

Warning! Warning! Warning! ... This article is my cookbook. It is designed for binary type update (two stages deployment) and only as reference. You can use it but it may not be suitable for all configurations. Use common sense and add / modify / repeat commands if necessary. I am doing same during update.

1. Update local repository

eix-sync

or

emerge --sync

or (if repository is synced)

eix-update

2. Clean logs from previous update

find /var/log/portage -maxdepth 1 -type f -ls -delete

3. Clean distfiles and package directory

eclean-dist -d ; eclean-pkg -d

4. Update system including build dependencies

4a. on "build" system

emerge --ask --update --deep --newuse --with-bdeps=y @world

4b. on "prod" system

emerge --ask --update --deep --newuse --with-bdeps=y --binpkg-changed-deps=n @world

5. Commit or reject configuration changes in "/etc"

etc-update

6. Review messages from packages

elogv

7. Clean packages with no dependency on "world" package set

emerge --ask --depclean

8. Scan for broken dependencies

• python:

python-updater --pretend

• perl:

perl-cleaner --all --pretend

• libraries detected by system:

emerge -ask @preserved-rebuild

• libraries not detected by portage:

revdep-rebuild    --ignore --pretend

revdep-rebuild.sh --ignore --pretend

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.