From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [OT] emerge default opts
Date: Sun, 15 Oct 2017 09:46:26 -0500 [thread overview]
Message-ID: <e999d771-b31d-d9a7-e7ce-a2457de26dac@gmail.com> (raw)
In-Reply-To: <f9f9e4fb-a1a4-6727-5ec7-6084cee8d689@gentoo.org>
Michael Orlitzky wrote:
> On 10/14/2017 09:30 PM, Dale wrote:
>> While at it. Is there a tool that tells when USE flags in make.conf is
>> either no longer used or doesn't even exist anymore?
> I don't know of one. It doesn't *sound* hard, but you would have to
> consider local use flags, flags from overlays, USE_EXPAND flags,
> wildcards, USE_ORDER, etc. -- so maybe it's actually hard/slow to do it.
>
> I found this feature request,
>
> https://github.com/vaeth/eix/issues/38
>
> and I guess that confirms that it's harder than it looks. Checking for
> nonexistent flags would be easier than checking for redundant flags
> because the latter depends on your package manager configuration.
>
>
I was thinking it may be harder than one thinks since I don't know of a
way to do it but have seen some who want something that does it. I'd be
happy if it just told me what USE flags no longer exist at all. My USE
line in make.conf is quite lengthy. I'm certain a lot of it could be
gone. Some may not have existed for years.
Maybe one day. Just maybe.
Thanks
Dale
:-) :-)
next prev parent reply other threads:[~2017-10-15 14:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-14 10:01 [gentoo-user] emerge --emptytree : how to ? Helmut Jarausch
2017-10-14 11:25 ` Dale
2017-10-15 0:26 ` [gentoo-user] [OT] emerge default opts Michael Orlitzky
2017-10-15 1:30 ` Dale
2017-10-15 14:31 ` Michael Orlitzky
2017-10-15 14:46 ` Dale [this message]
2017-10-15 15:36 ` Neil Bothwick
2017-10-15 18:47 ` Alan McKinnon
2017-10-15 20:39 ` Rich Freeman
2017-10-15 21:47 ` Bill Kenworthy
2017-10-20 2:23 ` Michael Orlitzky
2017-10-16 1:51 ` [gentoo-user] emerge --emptytree : how to ? Walter Dnes
2017-10-16 2:35 ` R0b0t1
2017-10-16 2:38 ` 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=e999d771-b31d-d9a7-e7ce-a2457de26dac@gmail.com \
--to=rdalek1967@gmail.com \
--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