| 1 |
Alexander Kirillov schreef: |
| 2 |
>>> Is there a way to list all ebuilds which need to be remerged |
| 3 |
>>> after kernel upgrade? Would be nice to have a special emerge |
| 4 |
>>> target for this very thing to happen automatically. |
| 5 |
>> |
| 6 |
>> |
| 7 |
>> emerge -v $( equery b /lib/modules | sed -e 's:^:>=:' ) |
| 8 |
> |
| 9 |
> |
| 10 |
> Thanks Peter, Found a module I forgot to rebuild using equery b |
| 11 |
> /lib/modules:) On the other hand splashutils need to be remerged |
| 12 |
> sometimes afaik. And vmware drivers. |
| 13 |
> |
| 14 |
|
| 15 |
Yes, I noticed that, too-- when I last tried Peter's command after a |
| 16 |
kernel update, I surprisingly got x11-xorg as a result (which was good), |
| 17 |
but not the ati-drivers, iirc, and also not splashutils (which, as you |
| 18 |
say, does sometimes need re-emerging, though I haven't quite figured out |
| 19 |
what precisely is the trigger, and I don't use vmware). |
| 20 |
|
| 21 |
I meant to ask about that, because while the command does seem to catch |
| 22 |
some modules that I didn't know needed to be re-emerged when upgrading |
| 23 |
the kernel, it seems to miss some that I know do, but I don't know |
| 24 |
enough about the issue to know why. |
| 25 |
|
| 26 |
Holly |
| 27 |
-- |
| 28 |
gentoo-user@g.o mailing list |
Archives