public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: flag details
Date: Mon, 24 Nov 2014 13:29:28 -0500	[thread overview]
Message-ID: <54737908.40702@gentoo.org> (raw)
In-Reply-To: <loom.20141124T191707-33@post.gmane.org>

On 11/24/2014 01:19 PM, James wrote:
> Jc García <jyo.garcia <at> gmail.com> writes:
> 
> 
>> 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.
> 
> yea that helps. But the information is a terse, single phrase usually.
> I'm looking for something (if it exists) that is more detailed
> about the flag usage and issues. Maybe nothing exists? Maybe
> it's only avaiable reading the sources?
> 

Basically. It kinda sucks. To fix it, we'd need a policy that every
ebuild has to properly document each of its USE flags in metadata.xml,
which means explaining how it actually affects the package, and not just
"enables libfoo." Then we'd need a repoman check to bitch at people who
don't do it.

Personally I'd be strongly for such a policy, even if it means every
package in the tree would become "in violation" overnight. This is
something that users could easily help with, by posting updated
metadata.xml on b.g.o.



  reply	other threads:[~2014-11-24 18:29 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 [this message]
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=54737908.40702@gentoo.org \
    --to=mjo@gentoo.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