From: "Christopher J. Camisa" <chris@camisa.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Cleaning out /etc/portage easily??
Date: Wed, 1 Jun 2016 02:37:19 -0500 [thread overview]
Message-ID: <829464aa-90df-3e1e-137a-625b493822c7@camisa.org> (raw)
In-Reply-To: <574E8E9A.4050604@gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1101 bytes --]
On 06/01/2016 02:28 AM, Dale wrote:
> Howdy,
>
> I suspect there may be more people than me wondering about this one. I
> have quite a few entries in /etc/portage files, especially keywords.
> I'd like to know if there is a tool that deletes no longer needed
> entries itself. I been using eix-test-obsolete but doing it manually
> can take quite a while. Is there a tool that I can run and it clean out
> those files itself instead of me doing it one line at a time? I figure
> there has to be someone out there that has already done this, surely.
>
> Anyone have any info on such a beast?
>
> Thanks much.
>
> Dale
>
> :-) :-)
>
>
>
Hi Dale,
You're looking for enalyze from app-portage/gentoolkit.
Have a look in the manual, ENALYZE(1) for usage.
DESCRIPTION
Enalyze is a collection of modules for analyzing the state of
installed Gentoo packages for USE flags or
keywords used for installation, and their current masking status.
It can also optionally (re)generate new /etc/portage/package.* files.
Kind Regards,
-Camisa
[-- Attachment #1.1.2: Type: text/html, Size: 1592 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-06-01 7:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 7:28 [gentoo-user] Cleaning out /etc/portage easily?? Dale
2016-06-01 7:37 ` Christopher J. Camisa [this message]
2016-06-01 7:46 ` Dale
2016-06-01 8:56 ` Dale
2016-06-01 9:00 ` Christopher J. Camisa
2016-06-01 9:15 ` Dale
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=829464aa-90df-3e1e-137a-625b493822c7@camisa.org \
--to=chris@camisa.org \
--cc=gentoo-user@lists.gentoo.org \
/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