| 1 |
n952162 wrote: |
| 2 |
> On 5/15/21 7:24 AM, Dan Egli wrote: |
| 3 |
>> The R status means REBUILD. Usually, if it's an @world it's pulling |
| 4 |
>> that in because something about that package changed and so it needs |
| 5 |
>> to rebuild it. The --noreplace option would block that if portage |
| 6 |
>> didn't think it was needed. Based on your options, I'd say that it's |
| 7 |
>> probably a USE flag was changed. I don't use binpkgs myself, |
| 8 |
>> preferring to compile except in certain circumstances (can we say |
| 9 |
>> RUST!?) that I need to use a -bin variant. You can try without it, but |
| 10 |
>> I recommend leaving your change-use and newuse flags in place and |
| 11 |
>> letting the system rebuild xmodmap. |
| 12 |
>> |
| 13 |
>> |
| 14 |
> Yes, thank you, but neither the server nor the client have any USE flags |
| 15 |
> for that package defined. And the package has to be pretty stable by |
| 16 |
> now ;-) |
| 17 |
> |
| 18 |
> |
| 19 |
> |
| 20 |
> |
| 21 |
|
| 22 |
All packages have USE flags defined somewhere even if you haven't |
| 23 |
defined any yourself. Some are defined in profiles, some are defined |
| 24 |
elsewhere. When I do updates, I see changes to USE flags all the time |
| 25 |
that were changed by the profile, the maintainer in the ebuild or |
| 26 |
somewhere else. After all, if a package doesn't have the USE flags |
| 27 |
defined somewhere, emerge won't know what USE flags to include or |
| 28 |
exclude support for. |
| 29 |
|
| 30 |
Dale |
| 31 |
|
| 32 |
:-) :-) |
Archives