From: Leho Kraav <leho@kraav.com>
To: linux.gentoo.user@googlegroups.com
Cc: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Consistency checking
Date: Wed, 2 Nov 2011 06:01:28 -0700 (PDT) [thread overview]
Message-ID: <24889171.1639.1320238888584.JavaMail.geo-discussion-forums@yqhd1> (raw)
In-Reply-To: <hSHXs-Yc-9@gated-at.bofh.it>
On Wednesday, November 2, 2011 2:20:02 PM UTC+2, Urs Schutz wrote:
> > eix-test-obsolete -d
> is easy if it is done often, as there is little corrective
> action to do on a day to day basis.
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.
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.
After that, the machine readable output needs to be as simple as possible, no colors, parenthesis, and whatnot.
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.
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.
next parent reply other threads:[~2011-11-02 13:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <hSdwm-cK-11@gated-at.bofh.it>
[not found] ` <hSq0y-4uf-25@gated-at.bofh.it>
[not found] ` <hSqWC-657-23@gated-at.bofh.it>
[not found] ` <hSHXs-Yc-9@gated-at.bofh.it>
2011-11-02 13:01 ` Leho Kraav [this message]
2011-11-02 13:12 ` [gentoo-user] Consistency checking Urs Schutz
2011-11-01 3:45 meino.cramer
2011-11-01 13:14 ` YoYo Siska
2011-11-01 13:16 ` Mark Knecht
2011-11-01 17:00 ` Urs Schutz
2011-11-01 18:00 ` meino.cramer
2011-11-01 20:40 ` Dale
2011-11-02 12:09 ` Urs Schutz
2011-11-02 14:06 ` Neil Bothwick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=24889171.1639.1320238888584.JavaMail.geo-discussion-forums@yqhd1 \
--to=leho@kraav.com \
--cc=gentoo-user@lists.gentoo.org \
--cc=linux.gentoo.user@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox