From: Bill Kenworthy <billk@iinet.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [OT] emerge default opts
Date: Mon, 16 Oct 2017 05:47:43 +0800 [thread overview]
Message-ID: <9823d4d2-4d68-7f82-95da-ecb2492923f4@iinet.net.au> (raw)
In-Reply-To: <CAGfcS_=a-jsbYxR7O2-mKaud8=Tmpt_o6NEe34oWX3AU+FaHKg@mail.gmail.com>
On 16/10/17 04:39, Rich Freeman wrote:
> On Sun, Oct 15, 2017 at 11:47 AM, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
>> On 15/10/2017 16:31, 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.
>>>
>>
>> There is a suitable tool. It's called grep, copious use of.
>> A suitably complex solution for the complexity of the problem!
>>
>
> Or you could just use portpeek...
>
moriah ~ # euse -i flag
global use flags (searching: flag)
************************************************************
no matching entries found
local use flags (searching: flag)
************************************************************
no matching entries found
moriah ~ #
BillK
next prev parent reply other threads:[~2017-10-15 21:47 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
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 [this message]
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=9823d4d2-4d68-7f82-95da-ecb2492923f4@iinet.net.au \
--to=billk@iinet.net.au \
--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