| 1 |
On Wednesday, November 2, 2011 2:20:02 PM UTC+2, Urs Schutz wrote: |
| 2 |
> > eix-test-obsolete -d |
| 3 |
> is easy if it is done often, as there is little corrective |
| 4 |
> action to do on a day to day basis. |
| 5 |
|
| 6 |
I have been wondering if it's possible to get this particular check's output to be machine readable, so it could be used in automated scripts. Similar to what qlist -IC <atom> does. |
| 7 |
|
| 8 |
First, I think the different checks need to be separatable with cmdline arguments, so one wouldn't have to start parsing for some header type thing to know what atom list applies to what file. |
| 9 |
|
| 10 |
After that, the machine readable output needs to be as simple as possible, no colors, parenthesis, and whatnot. |
| 11 |
|
| 12 |
Further thoughts welcome, and suggestions for other ways of automating this cleanup. Only thing I know of was udept, but that's been dead upstream for a while. |
| 13 |
|
| 14 |
I should also note that I keep my /etc in git, so naturally all automated actions would be commited and therefore tracked - no need to fear losing some important configuration item, if that is at all applicable here even. |
Archives