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