1 |
On Saturday, 30 January 2021 15:20:42 GMT Arve Barsnes wrote: |
2 |
> On Sat, 30 Jan 2021 at 15:58, Dr Rainer Woitok <rainer.woitok@×××××.com> |
3 |
wrote: |
4 |
> > Since I've installed Gentoo more than a year back I have a small script |
5 |
> > in "/etc/portage/postsync.d/" which just contains |
6 |
> > |
7 |
> > #! /bin/bash |
8 |
> > emerge --ask --changed-deps --changed-use --deep --newuse --oneshot \ |
9 |
> > |
10 |
> > --update --with-bdeps=y sys-apps/portage |
11 |
> > |
12 |
> > I'm not sure where I got that from, I thought it was in the Gentoo Hand- |
13 |
> > book, but looking there just now I didn't find anything like that. May- |
14 |
> > be I invented that myself. |
15 |
> > |
16 |
> > Am I interpreting you correctly that such a postsync hook is never nec- |
17 |
> > essary, that is, that the "portage" package itself is always a built-in |
18 |
> > build dependency for every other package? |
19 |
> |
20 |
> No, it is not a build dependency, but it is a part of the @system set, |
21 |
> so it will always be included in any @system or @world updates you do. |
22 |
> I would not bother updating it especially. |
23 |
> |
24 |
> Regards, |
25 |
> Arve |
26 |
|
27 |
Yes, what Arve said. |
28 |
|
29 |
Updating portage manually, whether using a postsync script like Rainer or not, |
30 |
is not necessary. However, it will not hurt, as long as the rest of the |
31 |
system is in a healthy state at the time. Trying to manually resolve issues |
32 |
with changed/obsolete USE flags, changing deps, python being half way through |
33 |
an upgrade, dangling symlinks, etc., will also not hurt, as long as you *know* |
34 |
what you're doing and are able to navigate your way through such transient |
35 |
problems. |
36 |
|
37 |
Letting portage update itself and its dependencies in the order it deems to be |
38 |
optimal invariably works without drama, even at 4:00 am. I am grateful to the |
39 |
Gentoo devs for this. :-) |