On Sat, 30 Jan 2021 17:55:21 +0100, Arve Barsnes wrote: > > Ok. But what if I just do, say > > > > emerge --ask --changed-deps --changed-use --deep --newuse \ > > --update --with-bdeps=y firefox > > > > after syncing? Is this, too, guaranteed to always work, even if > > portage itself is requiring an essential update? > > Unless you're years behind on your portage updates, there should be no > chance of getting any problems with this that could be fixed by > upgrading portage.
Unless you have a new Firefox ebuild released using a new EAPI version that is only in a later version of portage - an unlikely, but not impossible, scenario. > As long as you do world updates now and then, I > don't think you'd ever have any problems. I stopped updating portage > on its own many years ago, it's been fine. Same here. Most problems with portage are caused by people trying to fix supposed problems with portage :( -- Neil Bothwick I'm moving to theory. Everything works there!
pgpFTVH1jhoZf.pgp
Description: OpenPGP digital signature
