public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Undocumented and unused USE variables
Date: Fri, 16 Mar 2012 09:01:43 -0400	[thread overview]
Message-ID: <CAGfcS_m+rUAcYq1G8+AXWEep3umwMbThc9Lts7PDEOj+7+S9Ug@mail.gmail.com> (raw)
In-Reply-To: <htxybspj344g6ehbt7wfaldp.1331902164429@email.android.com>

On Fri, Mar 16, 2012 at 8:49 AM, Christoph Niethammer
<christoph.niethammer@googlemail.com> wrote:
> Here the euse command is realy handy. :-)
> However the sysfs USE flag is still hiding its documentation.
> So lets see if this is a bug or a feature. ;-)

Yup, euse is helpful, or you can grep /usr/portage/profiles/use.*
(including the local version).

I suspect we'll find 3 categories here:

1.  Stuff like amd64 which isn't really a USE flag proper, but which
is required due to how arch support works.  As far as I know amd64 is
the only one in this category.

2.  Stuff like pango which really are documented.

3.  Stuff like sysfs which are neither.  File a bug...  :)

Rich



  reply	other threads:[~2012-03-16 13:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-16 12:49 [gentoo-dev] Undocumented and unused USE variables Christoph Niethammer
2012-03-16 13:01 ` Rich Freeman [this message]
2012-03-16 17:53   ` [gentoo-dev] " Duncan
2012-03-16 16:55 ` [gentoo-dev] " Alec Warner
  -- strict thread matches above, loose matches on Subject: below --
2012-03-16 12:05 Christoph Niethammer
2012-03-16 12:12 ` Jory A. Pratt
2012-03-16 12:30 ` René Neumann
2012-03-16 13:01 ` Kent Fredric
2012-03-16 13:29 ` Joshua Kinard

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=CAGfcS_m+rUAcYq1G8+AXWEep3umwMbThc9Lts7PDEOj+7+S9Ug@mail.gmail.com \
    --to=rich0@gentoo.org \
    --cc=gentoo-dev@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