| 1 |
On Tue, 01 Jun 2010 19:46:33 +1000, Jake Moe wrote: |
| 2 |
|
| 3 |
> My question is: is there a way that Portage can compare what's |
| 4 |
> currently on the hard disk with what it installed, and do some sort of |
| 5 |
> checksum verification on it? |
| 6 |
|
| 7 |
Portage records a checksum for each file it installs, that's how it known |
| 8 |
not to delete files that were not installed by the ebuild it is |
| 9 |
unmerging. equery has an option to check packages against these |
| 10 |
|
| 11 |
equery check --only-failures '*' |
| 12 |
|
| 13 |
Note that it will show failures on any files that have been modified |
| 14 |
since installation, such as configuration and data files, so you'll have |
| 15 |
to check these manually, but if a library or executable shows up you |
| 16 |
almost certainly have a problem. |
| 17 |
|
| 18 |
|
| 19 |
-- |
| 20 |
Neil Bothwick |
| 21 |
|
| 22 |
Wow! That lightning sounds clo..zzzzit!" NO CARRIER |
Archives