From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 45B2A1389E2 for ; Mon, 24 Nov 2014 18:29:39 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 9E8C5E0897; Mon, 24 Nov 2014 18:29:34 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 54BB1E0807 for ; Mon, 24 Nov 2014 18:29:33 +0000 (UTC) Received: from [192.168.1.100] (c-98-218-46-55.hsd1.md.comcast.net [98.218.46.55]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mjo) by smtp.gentoo.org (Postfix) with ESMTPSA id 324D13401CA for ; Mon, 24 Nov 2014 18:29:32 +0000 (UTC) Message-ID: <54737908.40702@gentoo.org> Date: Mon, 24 Nov 2014 13:29:28 -0500 From: Michael Orlitzky User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.8.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: flag details References: In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Archives-Salt: 29f16450-21b7-41b7-b602-7c66975a1e90 X-Archives-Hash: 949794a480a485d3d9aa3190e2bf4983 On 11/24/2014 01:19 PM, James wrote: > Jc García 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.