1 |
On Sun, 20 Feb 2022 at 15:40, Dr Rainer Woitok <rainer.woitok@×××××.com> wrote: |
2 |
> But if I understand the "emerge" manual page correctly, "--changed-deps" |
3 |
> causes a rebuild of a package, if one of its dependencies has been re- |
4 |
> build, even though the package does not require the newer version of the |
5 |
> dependency. So does it really make sense to have this option hardcoded |
6 |
> in a script? Or does it just cause plenty of package rebuilds without |
7 |
> any real effect? Likewise, what about "--deep"? Should I keep it? |
8 |
|
9 |
"--deep" seems like a good idea, to minimise the chance of trouble, |
10 |
but "--changed-deps" does indeed seem excessive. |
11 |
|
12 |
I also have "--oneshot" in my updates, although I'm not sure if this |
13 |
actually makes a difference on a world update. |
14 |
|
15 |
I also have "--backtrack=100" to minimise the risk of portage not |
16 |
being able to find an upgrade path for some troublesome package. Just |
17 |
as "--deep" it will add to the time portage needs to calculate what |
18 |
packages to update, but it feels like I've had less instances of |
19 |
upgrade path troubles since adding it to my regular world update |
20 |
command. |
21 |
|
22 |
Regards, |
23 |
Arve |