| 1 |
On 14/08/2021 22:20, Ramon Fischer wrote: |
| 2 |
> Is there any way to tell "portage", that packages like "qtwebengine", |
| 3 |
> "(ungoogled-)chromium", "firefox" and so on are always compiled as last |
| 4 |
> package? |
| 5 |
|
| 6 |
The simplest way is to exclude those packages in the first update, and |
| 7 |
then allow them in the second: |
| 8 |
|
| 9 |
emerge -uDU @world --exclude "qtwebengine firefox chromium" && emerge |
| 10 |
-uDU @world |
| 11 |
|
| 12 |
The dependency tracker of portage will of course also exclude packages |
| 13 |
that depend on the excluded packages, unless they themselves have |
| 14 |
updates pending. In that case, they *might* get built twice; once |
| 15 |
against the current version of the excluded packages, and then perhaps |
| 16 |
again on the second run, if there's rebuild triggers involved. |
| 17 |
|
| 18 |
Most of the time though, you won't run into cases of redundant rebuilds. |
| 19 |
Rebuild triggers are not very common. |
Archives