| 1 |
On 06/03/2019 14:39, Mick wrote: |
| 2 |
> To date I have not found, or cannot recall, an occasion where revdep-rebuild |
| 3 |
> rebuilt anything following a run of @preserved-rebuild. I have stopped |
| 4 |
> running revdep-rebuild.sh for years now thinking it is redundant. |
| 5 |
|
| 6 |
@preserved-rebuild is only able to detect cases where the actual library |
| 7 |
file (*.so) got deleted. If the file is still there but there's runtime |
| 8 |
linking issues, it's not gonna find them. revdep-rebuild does find them, |
| 9 |
but not all of them. revdep-rebuild.sh finds cases revdep-rebuild does not. |
| 10 |
|
| 11 |
It seems that the safest option is to run "emerge -a @preserved-rebuild" |
| 12 |
first, then "revdep-rebuild -i -- -a" and finally "revdep-rebuild.sh -i |
| 13 |
-- -a". (The "-- -a" is just so emerge asks you before emerging anything.) |
Archives