public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] override PYTHON_TARGETS to avoid a slot collision
Date: Wed, 16 Dec 2020 06:25:47 -0600	[thread overview]
Message-ID: <0f6e32b6-f31c-f682-d347-6ea0f40405cc@gmail.com> (raw)
In-Reply-To: <CAM8Dd_0-v_XOKO6rr4OfA0-xcaOYSRMY-Hfzg_9rDU4zBTwFsA@mail.gmail.com>

Miles Malone wrote:
> Personally I just like to see what I'm getting myself into before I
> start doing an upgrade or recompile on all of chromium, firefox,
> qt-webkit, gtk-webkit, qt-webengine, libreoffice, and electron all at
> once :p
> To quote the meme, this little manouver's going to take us 51 years
>
>

That's true for me too.  I sometimes do my updates in a chroot and then
install binaries on my main install when it is done.  It's also a good
idea to check the USE flag changes as well.  Sometimes a new USE flag is
added or one that used to default to enabled is now defaulting to
disabled or vice versa.  If you see the change, it gives you a chance to
edit the correct config file to get the result you want.  Before -a came
along, everyone did a -p which meant removing the -p and running again
to do a update.  The -a gives you a chance to look and then proceed if
all looks right without having to run emerge again.  Sometimes it can
take a while for emerge to process what gets done. 

It's rare, very rare, that I run a emerge command without -a.  I always
check what will be done first. 

Dale

:-)  :-) 


  reply	other threads:[~2020-12-16 12:26 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-16 10:24 [gentoo-user] override PYTHON_TARGETS to avoid a slot collision n952162
2020-12-16 10:34 ` Miles Malone
2020-12-16 10:59   ` Arve Barsnes
2020-12-19 10:20     ` n952162
2020-12-19 10:45       ` William Kenworthy
2020-12-19 11:15         ` n952162
2020-12-19 10:56       ` Arve Barsnes
2020-12-19 11:12         ` n952162
2020-12-19 11:35           ` Neil Bothwick
2020-12-19 14:19             ` n952162
2020-12-19 15:49               ` Neil Bothwick
2020-12-19 12:34           ` Arve Barsnes
2020-12-19 11:12       ` bobwxc
2020-12-19 11:33         ` n952162
2020-12-19 11:37           ` Neil Bothwick
2020-12-19 11:51             ` Michael
2020-12-19 12:02               ` Jude DaShiell
2020-12-19 11:35       ` Michael
2020-12-19 14:11         ` n952162
2020-12-19 15:54           ` Neil Bothwick
2020-12-19 16:13             ` Dale
2020-12-20 13:58       ` Róbert Čerňanský
2020-12-16 11:07   ` n952162
2020-12-16 11:20     ` Miles Malone
2020-12-16 11:22     ` Miles Malone
2020-12-16 12:25       ` Dale [this message]
2020-12-19  9:39   ` n952162
2020-12-16 10:56 ` bobwxc

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=0f6e32b6-f31c-f682-d347-6ea0f40405cc@gmail.com \
    --to=rdalek1967@gmail.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