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 04:00:54 -0500 [thread overview]
Message-ID: <4c7a0c46-3e6c-69cd-d321-a87de4872342@camisa.org> (raw)
In-Reply-To: <574EA335.4070006@gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 3975 bytes --]
On 06/01/2016 03:56 AM, Dale wrote:
> Dale wrote:
>> Christopher J. Camisa wrote:
>>> 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
>>
>> That looks veeeerrryyyy interesting. That just may be what I need.
>> It seems to do it backwards from what I was expecting but I'll give
>> it a shot, once I read how to use it. ;-)
>>
>> Thanks much.
>>
>> Dale
>>
>> :-) :-)
>
>
> OK. Did a little reading on this and gave it a test run. It doesn't
> generate quite what I was expecting. This is a sample of what it
> generates.
>
>
> kde-plasma/kde-cli-tools ~amd64
> kde-plasma/kde-gtk-config ~amd64
> kde-plasma/kdecoration ~amd64
> kde-plasma/kdeplasma-addons ~amd64
> kde-plasma/kgamma ~amd64
> kde-plasma/khotkeys ~amd64
> kde-plasma/kinfocenter ~amd64
> kde-plasma/kmenuedit ~amd64
> kde-plasma/kscreen ~amd64
> kde-plasma/kscreenlocker ~amd64
> kde-plasma/ksshaskpass ~amd64
> kde-plasma/ksysguard ~amd64
> kde-plasma/kwallet-pam ~amd64
> kde-plasma/kwayland-integration ~amd64
> kde-plasma/kwin ~amd64
> kde-plasma/kwrited ~amd64
> kde-plasma/libkscreen ~amd64
>
>
> This is a example of what I currently have in my keyword file.
>
>
> # required by kde-plasma/plasma-meta-5.6.4::gentoo
> # required by @selected
> # required by @world (argument)
> =kde-plasma/plasma-workspace-5.6.4 ~amd64
> # required by kde-plasma/plasma-desktop-5.6.4::gentoo
> # required by kde-plasma/plasma-meta-5.6.4::gentoo
> # required by @selected
> # required by @world (argument)
> =kde-frameworks/karchive-5.22.0 ~amd64
> # required by kde-plasma/plasma-meta-5.6.4::gentoo
> # required by @selected
> # required by @world (argument)
> =kde-plasma/kinfocenter-5.6.4 ~amd64
> # required by kde-plasma/plasma-workspace-5.6.4::gentoo
> # required by kde-plasma/plasma-meta-5.6.4::gentoo
> # required by @selected
> # required by @world (argument)
> =kde-plasma/kwin-5.6.4 ~amd64
>
>
> The output of what emerge gives includes a version. The enalyze
> program seems to leave that out which may lead to upgrades that I'm
> not looking for yet.
>
> What I was hoping for, something that would for example see that
> plasma-workspace-5.6.4 is either no longer installed or no longer
> keyworded and can be removed from the file and then remove it.
> Honestly, I'm not a scripting guru but I sort of think it would be a
> hard thing to do given that basically every line would have to be
> checked. Also, the commented part above it would be deleted to in a
> ideal world. That to would be difficult since not all lines have
> those above it.
>
> Hmmmm. Gonna see what else it can do.
>
> Dale
>
> :-) :-)
Hi Dale,
Try again, but this time use the --exact option to your invocation
on the command line.
Kind Regards,
-Camisa
[-- Attachment #1.1.2: Type: text/html, Size: 5932 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-06-01 9:01 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
2016-06-01 7:46 ` Dale
2016-06-01 8:56 ` Dale
2016-06-01 9:00 ` Christopher J. Camisa [this message]
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=4c7a0c46-3e6c-69cd-d321-a87de4872342@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