• [gentoo-user] Re: Compile large packages as last package [SOLVED]

    From Ramon Fischer@21:1/5 to David M. Fellows on Wed Sep 8 22:00:01 2021
    To: gentoo-user@lists.gentoo.org

    --qTXenvXQb0ZbE4UJWDKC6Iaw5vsV3FKvs
    Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable
    Content-Language: en-US

    Thank you for the hint, but I am very aware of this.

    As the subject says, I want to compile large packages as last package,
    since it sometimes happens, that a large package may get compiled as
    package 245 of 300 for example; blocking other small packages.

    I just re-used "/etc/portage/package.env/no_tmpfs.conf", since it
    already contains a list of large packages, which most likely need a long
    time to compile.

    I should have been more elaborate in my last e-mail:

    I was actually hoping for a neat hack, where you can tag or
    prioritise (not nice or renice) packages in "/etc/portage/env/" or
    "/etc/portage/package.env/" to compile them as last packages.

    The solution with "--exclude" is working well so far; I had no redundant rebuilds. :)

    Maybe I need to tweak it later on, if rebuilds occur frequently, but
    this for another time.

    -Ramon

    On 08/09/2021 17:24, David M. Fellows wrote:
    Thank you for your ideas!

    I was actually hoping for a neat hack with "/etc/portage/env/" and
    "/etc/portage/package.env/", where you can set environment variables.
    Did you look at example 2 in https://wiki.gentoo.org/wiki//etc/portage/package.env ?

    It seems to address your problem.
    DaveF
    I will try out the following solution:

    $ < "/etc/portage/package.env/no_tmpfs.conf
    # custom - 20181121 - rfischer: list packages, which are too big for
    tmpfs
    #app-emulation/qemu-kv no_tmpfs.conf
    #app-office/libreoffice no_tmpfs.conf
    #dev-java/icedtea no_tmpfs.conf
    #dev-lang/ghc no_tmpfs.conf
    #dev-lang/rust no_tmpfs.conf
    #mail-client/thunderbird no_tmpfs.conf
    #sci-libs/tensorflow no_tmpfs.conf
    #sys-devel/gcc no_tmpfs.conf
    #www-client/firefox no_tmpfs.conf
    #www-client/ungoogled-chromium no_tmpfs.conf #throttle_make_emerge.conf >>
    $ < "${HOME}/bin/update.sh"
    [...]
    large_package_list=$(/bin/grep --extended-regexp --only-matching
    "[a-z]+-[a-z]+\/[-0-9a-zA-Z]+" "/etc/portage/package.env/no_tmpfs.conf") >> [...]
    /usr/bin/emerge --ask --update --deep --newuse --tree --verbose
    --exclude="${large_package_list//$'\n'/ }" @world
    /usr/bin/emerge --ask --update --deep --newuse --tree --verbose @world >>
    -Ramon

    On 15/08/2021 17:48, Nikos Chantziaras wrote:
    On 14/08/2021 22:20, Ramon Fischer wrote:
    Is there any way to tell "portage", that packages like "qtwebengine",
    "(ungoogled-)chromium", "firefox" and so on are always compiled as
    last package?
    The simplest way is to exclude those packages in the first update, and
    then allow them in the second:

    emerge -uDU @world --exclude "qtwebengine firefox chromium" && emerge
    -uDU @world

    The dependency tracker of portage will of course also exclude packages
    that depend on the excluded packages, unless they themselves have
    updates pending. In that case, they *might* get built twice; once
    against the current version of the excluded packages, and then perhaps
    again on the second run, if there's rebuild triggers involved.

    Most of the time though, you won't run into cases of redundant
    rebuilds. Rebuild triggers are not very common.


    --
    GPG public key: 5983 98DA 5F4D A464 38FD CF87 155B E264 13E6 99BF



    application/pgp-signature attachment, name=OpenPGP_signature

    --
    GPG public key: 5983 98DA 5F4D A464 38FD CF87 155B E264 13E6 99BF



    --qTXenvXQb0ZbE4UJWDKC6Iaw5vsV3FKvs--

    -----BEGIN PGP SIGNATURE-----

    wsF5BAABCAAjFiEEWYOY2l9NpGQ4/c+HFVviZBPmmb8FAmE5FbMFAwAAAAAACgkQFVviZBPmmb8A gBAA0jIo4J6ctyD5LhHW/HfjkZIkNEs+unU2vKzKOE9gi+Ng/+bzz+qHBhVmUquqGWwbM3gV2N9I 31aLEFDzlVd9Na6zTCIpIZPCXFICMKeMh/dWXiUmCWyFN0VZIioWZeXC3fQbEhQ5fc31zOHi2z9v 8+lUjSY0r5PrGgHhPTaQ3Yvw27b1on8YNkaNKskL6T1Jlm0+YZcED7o/0J4tMJ8tn4+T0IoJtisk 4I72LyE52k1O+jhUfBDWUwVrHe65TGcPLGk3+btwMb/CpXY0zCQCaNWHaEODyrDOo/TQ5epEF0dV utSRg1K5iJA84wSUOBTg1k3Q5r80aYeecpQek7bUqxf3Y4LrfJ6gN8gVTQNoXEHyDQs/t8Rp1TZ6 SSFP24fsunJ5jNVbm9D90Vot8e5RmJpYBqlmoVNyKLwQPSt0266Wrq9Zu4AXqx4xUZ3jcGsz3Tcg 9UgqBwdFik4ZRWGCrOruKT85O/6Lwn2WCXX83P/nTze2cKdyAFjWjZmha+qm1kNosb1SUe6TmYeu /UcmLVlX6a/UflJx1XQ0+Q82/TdZ5e+WXc6auT7hf34ni+Pf/KnetXK2/Lt+ARfWYH+yrxxOb7AV 2hIEPbOFtsNQQX6+3wd4IYZcjkYP0wuXvUqmlZepWC3VZhLIlbhVqyCn7NtpSsk0jnm1nZIQw0J3 e8A=
    =dV4m
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usen