| 1 |
Thank you for your ideas! |
| 2 |
|
| 3 |
I was actually hoping for a neat hack with "/etc/portage/env/" and |
| 4 |
"/etc/portage/package.env/", where you can set environment variables. |
| 5 |
|
| 6 |
I will try out the following solution: |
| 7 |
|
| 8 |
$ < "/etc/portage/package.env/no_tmpfs.conf |
| 9 |
# custom - 20181121 - rfischer: list packages, which are too big for |
| 10 |
tmpfs |
| 11 |
#app-emulation/qemu-kv no_tmpfs.conf |
| 12 |
#app-office/libreoffice no_tmpfs.conf |
| 13 |
#dev-java/icedtea no_tmpfs.conf |
| 14 |
#dev-lang/ghc no_tmpfs.conf |
| 15 |
#dev-lang/rust no_tmpfs.conf |
| 16 |
#mail-client/thunderbird no_tmpfs.conf |
| 17 |
#sci-libs/tensorflow no_tmpfs.conf |
| 18 |
#sys-devel/gcc no_tmpfs.conf |
| 19 |
#www-client/firefox no_tmpfs.conf |
| 20 |
#www-client/ungoogled-chromium no_tmpfs.conf #throttle_make_emerge.conf |
| 21 |
|
| 22 |
$ < "${HOME}/bin/update.sh" |
| 23 |
[...] |
| 24 |
large_package_list=$(/bin/grep --extended-regexp --only-matching |
| 25 |
"[a-z]+-[a-z]+\/[-0-9a-zA-Z]+" "/etc/portage/package.env/no_tmpfs.conf") |
| 26 |
[...] |
| 27 |
/usr/bin/emerge --ask --update --deep --newuse --tree --verbose |
| 28 |
--exclude="${large_package_list//$'\n'/ }" @world |
| 29 |
/usr/bin/emerge --ask --update --deep --newuse --tree --verbose @world |
| 30 |
|
| 31 |
-Ramon |
| 32 |
|
| 33 |
On 15/08/2021 17:48, Nikos Chantziaras wrote: |
| 34 |
> On 14/08/2021 22:20, Ramon Fischer wrote: |
| 35 |
>> Is there any way to tell "portage", that packages like "qtwebengine", |
| 36 |
>> "(ungoogled-)chromium", "firefox" and so on are always compiled as |
| 37 |
>> last package? |
| 38 |
> |
| 39 |
> The simplest way is to exclude those packages in the first update, and |
| 40 |
> then allow them in the second: |
| 41 |
> |
| 42 |
> emerge -uDU @world --exclude "qtwebengine firefox chromium" && emerge |
| 43 |
> -uDU @world |
| 44 |
> |
| 45 |
> The dependency tracker of portage will of course also exclude packages |
| 46 |
> that depend on the excluded packages, unless they themselves have |
| 47 |
> updates pending. In that case, they *might* get built twice; once |
| 48 |
> against the current version of the excluded packages, and then perhaps |
| 49 |
> again on the second run, if there's rebuild triggers involved. |
| 50 |
> |
| 51 |
> Most of the time though, you won't run into cases of redundant |
| 52 |
> rebuilds. Rebuild triggers are not very common. |
| 53 |
> |
| 54 |
> |
| 55 |
|
| 56 |
-- |
| 57 |
GPG public key: 5983 98DA 5F4D A464 38FD CF87 155B E264 13E6 99BF |
Archives