From: "Jc García" <jyo.garcia@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] flag details
Date: Mon, 24 Nov 2014 11:22:22 -0600 [thread overview]
Message-ID: <CAGQH77dV924rFUDn_j7gOsTpUWw06BToMiuuttw3=CJ96HfkPA@mail.gmail.com> (raw)
In-Reply-To: <loom.20141124T175621-87@post.gmane.org>
2014-11-24 11:09 GMT-06:00 James <wireless@tampabay.rr.com>:
> Hello,
>
>
> So, I use euse to read aobut flags. Sometimes the same flag has slightly,
> but significantly different meanings depending on the packages it
> is use on. A tool with perhaps more detail or that parse the ebuild/sources
> for even greater detail information?
>
> I also use Ciaran's old (filter)script on flags:
>
> explainuseflag(){ sed -ne "s,^\([^ ]*:\)\?$1 - ,,p" $(portageq
> portdir)/profiles/use.{,local.}desc; }
>
> Which is due for updating. If does a nice job of filtering out the
> package version details, which I do not need most of the time.
>
> Suggested fixes to Ciarans old filter quickie I use from by bashrc?
>
> Are there any more detailed tools, even gui based tools, for
> reading about the details of what a flag does on a given package
> or information related to compile-time or run-time settings on a
> given code (but not including looking at the sources, I know I can
> do that)?
>
> (Gmane on gentoo user is working again from a browser window (yea).
> Sorry for the recent noisy_posts.
>
>
I use
$ equery u cat/pkg
It list the useflags and what the metadata.xml of the package says
about each of them, plus highlights the active ones if you have the
package already merged.
> curiously,
> James
>
>
next prev parent reply other threads:[~2014-11-24 17:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 17:09 [gentoo-user] flag details James
2014-11-24 17:22 ` Jc García [this message]
2014-11-24 18:19 ` [gentoo-user] " James
2014-11-24 18:29 ` Michael Orlitzky
2014-11-24 18:37 ` Emanuele Rusconi
2014-11-24 18:58 ` James
2014-11-30 0:48 ` [gentoo-user] " Frank Steinmetzger
2014-11-30 15:16 ` [gentoo-user] " James
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='CAGQH77dV924rFUDn_j7gOsTpUWw06BToMiuuttw3=CJ96HfkPA@mail.gmail.com' \
--to=jyo.garcia@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