From: Christoph Niethammer <christoph.niethammer@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Undocumented and unused USE variables
Date: Fri, 16 Mar 2012 13:49:24 +0100 [thread overview]
Message-ID: <htxybspj344g6ehbt7wfaldp.1331902164429@email.android.com> (raw)
Hello.
I see. There is more documentation on a per package bases wich has to be considered, too. (Found already the metadata.xml files.)
As with the pango USE they may differe in their description - maybe also in their meaning for different packages. So local USE flags should only be used on a per package basis!
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. ;-)
Thx for the clarification so far.
Best regards
Christoph
René Neumann <lists@necoro.eu> schrieb:
>> * Undocumented use flags:
>> ----------
>> pango
>
>
>% euse -i pango
>global use flags (searching: pango)
>************************************************************
>no matching entries found
>
>local use flags (searching: pango)
>************************************************************
>[+ D ] pango
> app-i18n/fcitx: Enable support for x11-libs/pango
> 3.6.3 [gentoo]
> 3.6.4 [gentoo]
> [+ ] 4.0.0 [gentoo]
> [+ ] 4.0.1 [gentoo]
> [+ ] 4.2.0-r2 [gentoo]
> [+ ] 4.2.1 [gentoo]
>
>[+ D ] pango
> media-gfx/fontforge: Enable pango font rendering
> [+ ] 20100501 [gentoo]
> [+ ] 20110222 [gentoo]
> [+ ] 20110222-r1 [gentoo]
>
>[+ D ] pango
> media-gfx/imagemagick: Enable Pango support using x11-libs/pango
>
>[...]
>
next reply other threads:[~2012-03-16 12:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 12:49 Christoph Niethammer [this message]
2012-03-16 13:01 ` [gentoo-dev] Undocumented and unused USE variables Rich Freeman
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=htxybspj344g6ehbt7wfaldp.1331902164429@email.android.com \
--to=christoph.niethammer@googlemail.com \
--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