| 1 |
Is it a good practise to update @system first?
|
| 2 |
|
| 3 |
I always update @world almost every seven days and I only get into
|
| 4 |
package conflicts, if I do not update for more than 60 days or so. Last
|
| 5 |
time was 99 days ago and I had to resolve circular package dependencies
|
| 6 |
and so forth manually.
|
| 7 |
|
| 8 |
I wrote this update script[1] for my weekly update routine, where I am
|
| 9 |
still testing "--changed-use", instead of "--newuse":
|
| 10 |
|
| 11 |
[...]
|
| 12 |
no_tmpfs_file="/etc/portage/package.env/no_tmpfs.conf"
|
| 13 |
[...]
|
| 14 |
large_package_list=$(/bin/grep --extended-regexp --only-matching
|
| 15 |
"[0-9a-zA-Z]+-[0-9a-zA-Z]+\/[-0-9a-zA-Z]+" "${no_tmpfs_file}")
|
| 16 |
[...]
|
| 17 |
/usr/bin/eix-sync
|
| 18 |
if /usr/bin/eix --upgrade sys-apps/portage >/dev/null
|
| 19 |
then
|
| 20 |
/bin/echo -e "\e[01;31mA new version of 'sys-apps/portage' was
|
| 21 |
found. Updating it first...\e[0m"
|
| 22 |
/usr/bin/emerge --ask --oneshot sys-apps/portage
|
| 23 |
fi
|
| 24 |
/usr/bin/emerge --ask --update --deep --changed-use --tree --verbose
|
| 25 |
--exclude="${large_package_list//$'\n'/ }" @world
|
| 26 |
# always compile large packages as last packages
|
| 27 |
/usr/bin/emerge --update --deep --changed-use --tree --verbose @world
|
| 28 |
/usr/sbin/etc-update
|
| 29 |
/usr/bin/emerge --ask --depclean --verbose
|
| 30 |
/usr/bin/glsa-check --test all
|
| 31 |
/usr/bin/glsa-check --list
|
| 32 |
/usr/bin/glsa-check --fix --quiet all
|
| 33 |
/usr/bin/revdep-rebuild --verbose -- --ask
|
| 34 |
/usr/bin/eclean --deep --time-limit="1m" distfiles
|
| 35 |
/usr/bin/eclean --deep --time-limit="1m" packages
|
| 36 |
/usr/bin/eix-test-obsolete
|
| 37 |
/usr/bin/elogv
|
| 38 |
/usr/bin/eselect news read
|
| 39 |
|
| 40 |
-Ramon
|
| 41 |
|
| 42 |
[1]
|
| 43 |
https://codeberg.org/keks24/dotfiles/src/branch/master/root/bin/update.sh
|
| 44 |
|
| 45 |
On 22/02/2022 07:24, hitachi303 wrote:
|
| 46 |
> |
| 47 |
> Am 22.02.2022 um 06:27 schrieb Andreas Fink: |
| 48 |
>> On Mon, 21 Feb 2022 22:26:30 +0100 |
| 49 |
>> hitachi303 <gentoo-user@××××××××××××××××.de> wrote: |
| 50 |
>> |
| 51 |
>> |
| 52 |
>>> |
| 53 |
>>> emerge -av --depclean <every huge program which will be updated anyway. |
| 54 |
>>> Stuff like firefox, thunderbird, etc.> |
| 55 |
>>> |
| 56 |
>>> emerge -a --depclean --with-bdeps=n |
| 57 |
>>> |
| 58 |
>>> only then when there are as few programs installed as possible I run |
| 59 |
>>> emerge --sync |
| 60 |
>>> |
| 61 |
>>> emerge -Dua --reinstall changed-use @world |
| 62 |
>> I think what you really are doing can be simplified by: |
| 63 |
>> emerge -auvDN @system |
| 64 |
>> emerge -auvDN @world |
| 65 |
>> |
| 66 |
>> Once @system is updated it is much simpler to get @world to update too. |
| 67 |
>> Maybe you have to help with a couple of `--exclude ATOM` when updating |
| 68 |
>> world. |
| 69 |
> |
| 70 |
> From time to time I ran into trouble with @system where emerge |
| 71 |
> couldn't resolve blocks but using @world did not have this problems |
| 72 |
> and went fine. |
| 73 |
> |
| 74 |
|
| 75 |
--
|
| 76 |
GPG public key: 5983 98DA 5F4D A464 38FD CF87 155B E264 13E6 99BF |
Archives