On 2019.05.31 11:49, n952...@web.de wrote:
> Gesendet: Freitag, 31. Mai 2019 um 00:02 Uhr
> Von: "Dale" <rdalek1...@gmail.com>
> An: gentoo-user@lists.gentoo.org
> Betreff: Re: Aw: Re: [gentoo-user] upgrading (profiles, too)
>
> Mick wrote:
> > On Thursday, 30 May 2019 02:18:01 BST Dale wrote:
to do.
>
> If I recall correctly, I did a merge -e world when I switched to
17.0.
> There are some things that I'd rather rebuild everything just to be
> sure. When it is winter time, why not, I need the heat anyway.
;-)
>
> Dale
>
> :-) :-)
>
>
Compiling is not the problem. Knowing what USE and KEYWORD flags to
set is what scares me. At least those. I get all these dire
warnings from the system and I don't know what I did wrong. I'm
certainly not in the experimental class. I try to do the most
standard, stable things.
You may not have done anything wrong. How dire an emerge warning is is
up to interpretation. One way I sometimes deal with an update that
throws lots of warnings and requests to change masks or keywords or use
flags is to look carefully at the list of packages that would be
updated, and pick one, and just try to update that one. I even
sometimes find it easier to just "emerge -1 package" (instead of -u)
because that seems less likely to try to include updates not needed for
the package you selected.
Also - I don't think you ever said which (or at least how many)
packages you already have in packages.keyword. Often, having one
package in that file (especially if it is not for a single version)
will want testing versions of dependencies, so you either have to add
those, or not use the testing version of the first package.
Portage asking for changes to USE flags is likely far less of an issue
- sometimes packages are changed so that a dependency now requires a
particular use flag setting which is not the default (or may be
affected by some USE flag you have set (or unset) in make.conf.
