public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: flag details
Date: Mon, 24 Nov 2014 18:58:49 +0000 (UTC)	[thread overview]
Message-ID: <loom.20141124T195602-419@post.gmane.org> (raw)
In-Reply-To: CAPife4kZDbfwqAdVX8L-bnFTb3JhWR0t-Ch6bN6fY0-1sYi9Tg@mail.gmail.com

Emanuele Rusconi <emarsk <at> gmail.com> writes:


> When in doubt I just read the ebuild and try to understand what's 
> going on.  A policy would be nice, though, and sometimes even reading 
> the ebuild leaves me guessing.  As you point out, saying "foo: enables   
> libfoo" leaves me wandering "OK, but what the f* would I need foo for??"


I wonder if there is a reasonable why to extend app-portage/elogviewer

to parse more more details related to flags, or at leaset compile-time and
run-time details?


curiously,
James





  reply	other threads:[~2014-11-24 18:59 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
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 [this message]
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=loom.20141124T195602-419@post.gmane.org \
    --to=wireless@tampabay.rr.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