public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] emerge - Tips and Tricks
Date: Mon, 02 Sep 2024 09:06:56 +0100	[thread overview]
Message-ID: <2340049.ElGaqSPkdT@rogueboard> (raw)
In-Reply-To: <cc4e9e73-0abc-4926-9c9b-b6fc0c7fdbd7@youngman.org.uk>

[-- Attachment #1: Type: text/plain, Size: 1637 bytes --]

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!

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-09-02  8:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-01 22:44 [gentoo-user] emerge - Tips and Tricks Joe
2024-09-01 23:56 ` Dale
2024-09-02  1:59   ` Joe
2024-09-02  5:11     ` Dale
2024-09-02  6:59       ` Wols Lists
2024-09-02  8:06         ` Michael [this message]
2024-09-02  9:17           ` [gentoo-user] " Nuno Silva
2024-09-02  3:53   ` [gentoo-user] " Matt Connell
2024-09-02  5:13     ` Dale
2024-09-02  6:55   ` Wols Lists
2024-09-02  7:19     ` Dale
2024-09-02 15:11   ` ralfconn
2024-09-03  7:49     ` Dale
2024-09-03  9:05       ` Arve Barsnes
2024-09-03  9:05         ` Arve Barsnes
2024-09-03 10:32           ` Dale
2024-09-02 15:10 ` ralfconn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2340049.ElGaqSPkdT@rogueboard \
    --to=confabulate@kintzios.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox