public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Christoph Niethammer <christoph.niethammer@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Undocumented and unused USE variables
Date: Fri, 16 Mar 2012 13:05:27 +0100	[thread overview]
Message-ID: <1813960.lTJXjFAotk@elephant> (raw)

[-- Attachment #1: Type: text/plain, Size: 954 bytes --]

Hello.

Currently I am doing a from scratch installation of gentoo.

While setting up my USE flags I noticed, that some default USE flags in the 
default environment (default/linux/amd64/10.0/desktop/kde) are neither
documented (in /usr/portage/profiles/use.desc) nor used in IUSE by any package 
(amd64).

I am wondering if they are a leftover from older/outdated packages and could 
be removed.

Here is the list of USE flags I identified at my system:

* Undocumented use flags:
----------
amd64
consolekit
declarative
gdu
kipi
mudflap
nptlonly
pango
phonon
pppd
qt3support
sysfs
xorg

* Unused and undocumented USE flags:
----------
amd64
mudflap
sysfs


For those who want to search on their system I attached two scripts:
* find_undocumented_uses.sh : 
	searches for use flags which are active but not documenten in
	/usr/portage/profiles/use.desc.
* find_unused_uses.sh :
	Checks for given USE flags if they are found in any ebuild's IUSE statment

[-- Attachment #2: find_undocumented_uses.sh --]
[-- Type: application/x-shellscript, Size: 531 bytes --]

[-- Attachment #3: find_unused_uses.sh --]
[-- Type: application/x-shellscript, Size: 864 bytes --]

             reply	other threads:[~2012-03-16 12:06 UTC|newest]

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

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=1813960.lTJXjFAotk@elephant \
    --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