| 1 |
On 12/9/20 1:00 am, Matt Connell (Gmail) wrote: |
| 2 |
> On Sat, 2020-09-12 at 00:49 +0800, Andrew Lowe wrote: |
| 3 |
>> emerge --ask -NuD world |
| 4 |
> |
| 5 |
>> Is there a simple way of stopping this? |
| 6 |
> |
| 7 |
> Unless I'm mistaken, this is happening because of the -N flag to |
| 8 |
> emerge. Since the ABI changes/additions add *new USE flags* for |
| 9 |
> packages, when you tell emerge to rebuild packages on finding new/added |
| 10 |
> USE flags, it wants to rebuild them. |
| 11 |
> |
| 12 |
> I usually stick with -U (--changed-use) instead, when emerging world. |
| 13 |
> This only rebuilds packages when the flags *change*. Give that a go. |
| 14 |
> |
| 15 |
> |
| 16 |
|
| 17 |
Ahh, I see now what's going on. The problem is that if I do a "-uD" |
| 18 |
now, and get just the updates, it just "kicks the 290 further down the |
| 19 |
road" until I next do an "-NuD", which if memory serves has always been |
| 20 |
the recommended way of updating - according to the gentoo wiki/doco. I |
| 21 |
might as well get it over and done with now... |
| 22 |
|
| 23 |
Yes, just tested. "-uD" -> just updates. "-NuD" -> updates + 290 odd |
| 24 |
rebuilds. |
| 25 |
|
| 26 |
It's 02:30 Saturday morning in Perth Australia So I'll just kill it for |
| 27 |
now and kick it off tomorrow sometime. |
| 28 |
|
| 29 |
Thanks for the reply Matt, |
| 30 |
|
| 31 |
Andrew |
Archives