public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Humphrey <prh@gotadsl.co.uk>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] recommended USE flags
Date: Sat, 12 Aug 2006 11:13:01 +0100	[thread overview]
Message-ID: <200608121113.01942.prh@gotadsl.co.uk> (raw)
In-Reply-To: <200608120001.54438.volker.armin.hemmann@tu-clausthal.de>

On Friday 11 August 2006 23:01, Hemmann, Volker Armin wrote:

> install ufed
>
> as root:
> ufed
>
> then go down the list, read the descripition, think about it, decide,
> next flag, read descriptition, think about it, decide ...

I remember reading of a proposed overhaul of the USE flag documentation; has 
anything come of that? At the moment, many flags are described as "adds 
support for foo", but that is woefully inadequate. In some cases it means 
the inclusion of some extra code in packages to handle the data specified 
by the USE flag, whereas in others it implies a wholesale inclusion of 
reams of packages. Examples: 

-- 
~ # grep wmf /usr/portage/profiles/use.desc
wmf - Adds support for the wmf vector image format
~ # grep X /usr/portage/profiles/use.desc
X - Adds support for X11
-- 

In the wmf case, only a small amount of code is affected, but in the X case 
you get the entire X Window System!

Besides, the "adds support for foo" construction reminds me of BASIC 
programs we used to see 25 years ago, in which the programmer had included 
such gems as:

LET X=0;	REM set X to 0

What's needed is a brief explanation of what including foo implies, and I 
thought a plan was in place to do that. I'd be happy to help out with such 
an effort.

-- 
Rgds
Peter
-- 
gentoo-amd64@gentoo.org mailing list



  reply	other threads:[~2006-08-12 10:18 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-11 12:29 [gentoo-amd64] recommended USE flags Rafael Barrera Oro
2006-08-11 16:47 ` Ahmed Ammar
2006-08-11 17:03   ` Dan Clark
2006-08-11 18:31     ` Sam Barlow
2006-08-11 17:01 ` Roman Zilka
2006-08-11 22:01   ` [gentoo-amd64] " Duncan
2006-08-11 22:01 ` [gentoo-amd64] " Hemmann, Volker Armin
2006-08-12 10:13   ` Peter Humphrey [this message]
2006-08-12 12:39     ` [gentoo-amd64] " Duncan
2006-08-12 12:49       ` Simon Stelling
2006-08-12 18:44         ` [gentoo-amd64] " Duncan
2006-08-12 17:35       ` [gentoo-amd64] " Peter Humphrey
2006-08-12 18:35         ` [gentoo-amd64] " Duncan
2006-08-12 20:18           ` Hemmann, Volker Armin
2006-08-12 20:45             ` Vladimir G. Ivanovic
2006-08-12 20:58               ` Hemmann, Volker Armin
2006-08-13  8:48                 ` Peter Humphrey
2006-08-14  9:22                   ` Peter Humphrey
2006-08-13 10:17                 ` Simon Stelling
2006-08-13 10:20             ` [gentoo-amd64] " Duncan
2006-08-13 16:56               ` Hemmann, Volker Armin
2006-08-13 19:34                 ` [gentoo-amd64] " Duncan
2006-08-13 16:45           ` [gentoo-amd64] " Hemmann, Volker Armin
2006-08-14 12:16   ` [gentoo-amd64] " Conway S. Smith
2006-08-12  0:05 ` Richard Fish
2006-08-12 20:18   ` J'raxis 270145
2006-08-13  8:57     ` Peter Humphrey
2006-08-13 10:20       ` Simon Stelling
2006-08-13 10:43         ` Peter Humphrey

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=200608121113.01942.prh@gotadsl.co.uk \
    --to=prh@gotadsl.co.uk \
    --cc=gentoo-amd64@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