On 5/16/21 12:01 PM, Dale wrote:
n952162 wrote:
On 5/15/21 7:24 AM, Dan Egli wrote:
The R status means REBUILD. Usually, if it's an @world it's pulling
that in because something about that package changed and so it needs
to rebuild it. The --noreplace option would block that if portage
didn't think it was needed. Based on your options, I'd say that it's
probably a USE flag was changed. I don't use binpkgs myself,
preferring to compile except in certain circumstances (can we say
RUST!?) that I need to use a -bin variant. You can try without it, but
I recommend leaving your change-use and newuse flags in place and
letting the system rebuild xmodmap.
Yes, thank you, but neither the server nor the client have any USE flags
for that package defined. And the package has to be pretty stable by
now ;-)
All packages have USE flags defined somewhere even if you haven't
defined any yourself. Some are defined in profiles, some are defined
elsewhere. When I do updates, I see changes to USE flags all the time
that were changed by the profile, the maintainer in the ebuild or
somewhere else. After all, if a package doesn't have the USE flags
defined somewhere, emerge won't know what USE flags to include or
exclude support for.
Dale
:-) :-)
But if I don't specify that I want something specific, why should
portage say, this package has internal differences to the old package, I
better not install it?
