• Re: [gentoo-user] emerge - Tips and Tricks

    From Wols Lists@21:1/5 to Dale on Mon Sep 2 09:00:02 2024
    On 02/09/2024 06:11, Dale wrote:
    If you have a laptop where heat is a issue, you may want to do things different but if you can, that will give you the most stable system for updates.

    Another tip - if you run into any problems, try to emerge @system, not
    @world.

    If you know you've successfully emerged @system and you get loads of
    stuff blocking with an @world, I tend to just unmerge all the blockers
    until @world fires successfully. You need to be a bit careful, you could
    still unmerge something important, but it's unlikely. Although these
    problems also tend to be fixed by backtrack=100.

    Cheers,
    Wol

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Michael@21:1/5 to All on Mon Sep 2 09:06:56 2024
    On Monday, 2 September 2024 07:59:20 BST Wols Lists wrote:
    On 02/09/2024 06:11, Dale wrote:
    If you have a laptop where heat is a issue, you may want to do things different but if you can, that will give you the most stable system for updates.

    Another tip - if you run into any problems, try to emerge @system, not @world.

    If you know you've successfully emerged @system and you get loads of
    stuff blocking with an @world, I tend to just unmerge all the blockers
    until @world fires successfully. You need to be a bit careful, you could still unmerge something important, but it's unlikely. Although these
    problems also tend to be fixed by backtrack=100.

    Cheers,
    Wol

    You can remove blockers manually and I admit to do it occasionally, but it can sometimes break your system if you don't pay particular attention and you inadvertently remove some critical toolchain software - e.g. python, glibc, gcc, et al. It is safer to run:

    emerge --depclean -v -p <some_package>

    and check what dependencies of <some_package> are complaining about your attempt to remove it. Should you come across python or something portage depends on, it's best to back off and ask before you decide how to proceed. Soft blockers (b) are dealt with automatically by emerge, it is hard blockers (B) you'd have to pay attention to.

    My typical update runs like this:

    eix-sync
    emerge -uaNDv @world
    dispatch-conf
    emerge --depclean -a -v
    eclean-dist

    If the emerge output asks me to, I also run:

    revdep-rebuild

    and when perl itself goes through a major update, I run:

    perl-cleaner --reallyall

    Enjoy your gentoo!

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

    iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmbVciAACgkQseqq9sKV Zxlihg/+P1FKMzPDB4U9zud5ZdMxLxIB4hgXM4GOSmYejP1ynM+pC4xSUNQw8dvE 0V/m7J5LO3B9HOYbweUIUQ5iU2KuE0hT0z6egil5GUAYVZzcFH+252MMhKm/Wwzh gy2VmUUTGvOc3fwyBgvVbZIIz/qGizNurfsayPjR2D1Q6CcsV8taUkr5CKOZe/1I lscQ+WF3mwBl8l/1QQymOqAxfH9dRDinMPt5x1haDQcxYH3Sg0djHY8ed5jsZSSy KGB2rgykrg/RP0vaqa8qoEyB5yhOr7CV2/Rw+cHlli+cRLO903ENR2gGf92/uaac N0bAMhwX9+qpzTV8iOhEGBrqyEGSHkKEWCa4oRhvycDZdSs2e7OkC6N0dDEKOXr/ HoWrVqE2Uv0d8mI829FdSGfLeQ1yKc1/l+pv+mvWBnP+Q47hR5hVjACJN5nRe+eG xq0Yr0ZrJ62f5l0vLO/u8+w0t0BSPXyTBoDl9LDEqPQltivwppWdGC00yCsyucfk wLZBNBlcEtce36pfjJonti1JfwZHnDJxguGgCoPSvjLvc7qMH/fqn5x6CsL0NdGb Ap/kPUN3w8F8tM2wuYqpKlydVcYebP3FT8k8Nqus5iFkCR0wSUdDYaCmn1zsAm8M 0NJH1yPBD1qshpVVUxotZaF50zQrj4cTmw1rzxYw29xl1YO+e48=
    =C1zC
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From ralfconn@21:1/5 to All on Mon Sep 2 17:20:02 2024
    Il 02/09/24 00:44, Joe ha scritto:

    Normally i run emerge -uavDU --with-bdeps=y @world when i don't want a reinstall of everything after a emerge --sync

    I run emerge -uavDN --with-bdeps=y @world when i want to reinstall or
    like the manual says if there is a use flag that has been changed by me
    or the dev.


    My make.conf:

    EMERGE_DEFAULT_OPTS="--quiet-build --keep-going --jobs 24 --load-average
    24.0"
    MAKEOPTS="-j24 -l24.0"

    I don't know if I got the load-average and company right, anyway the
    system is always responsive (Ryzen 9 with 64Gb) even when using all 24
    CPU threads. The ebuilds have gotten a long way towards stability even
    in ~amd64, I rarely have build problems (except when cross-compiling for
    ARM, but that's a different story).

    My command line is 'emerge -auDvN @world'. Let the system decide if
    there are USE flag changes that require a rebuild, computers should do
    the boring stuff for us 🙂

    raf

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)