1 |
On 2020-12-05 01:04-0000 Grant Edwards <grant.b.edwards@×××××.com> |
2 |
wrote: |
3 |
|
4 |
> On 2020-12-04, tastytea <gentoo@××××××××.de> wrote: |
5 |
> > On 2020-12-04 17:39-0000 Grant Edwards <grant.b.edwards@×××××.com> |
6 |
> > wrote: |
7 |
> >> [...] |
8 |
> >> |
9 |
> >> I used to use 'python-updater' to take care of that, but it's |
10 |
> >> gone. What are we supposed to use in its place? |
11 |
> >> |
12 |
> >> Are we just supposed to manually re-emerge various python modules |
13 |
> >> over the next few weeks as we stumble across failures? |
14 |
> > |
15 |
> > emerge --changed-use --deep @world should take care of that. |
16 |
> |
17 |
> I always update with -ND (--newuse --deep) which I thought was |
18 |
> supposed to include what would be built by --changed-use, but maybe |
19 |
> I'm misunderstanding: |
20 |
|
21 |
--newuse and --changed-use are almost the same. The only difference is, |
22 |
as far as I know: |
23 |
|
24 |
--changed-use, -U |
25 |
[…] Unlike --newuse, the --changed-use option does not trigger |
26 |
reinstallation when flags that the user has not enabled are added or |
27 |
removed. |
28 |
|
29 |
I don't know why that didn't catch all python modules. |