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]  Re: Re: recommended USE flags
Date: Sun, 13 Aug 2006 09:48:53 +0100	[thread overview]
Message-ID: <200608130948.53413.prh@gotadsl.co.uk> (raw)
In-Reply-To: <200608122258.35615.volker.armin.hemmann@tu-clausthal.de>

On Saturday 12 August 2006 21:58, Hemmann, Volker Armin wrote:
> On Saturday 12 August 2006 22:45, Vladimir G. Ivanovic wrote:

> > His point is precisely that it's NOT useful enough.
>
> for him maybe.

But it is for most of us. I think the most important occasion of use of 
use.desc is on first installation. That file is already quite large and 
intimidating enough for the new user.

> > > concentrated in two files, you want the user to search all packages
> > > and read thousands of descriptions just to figure out if he wants the
> > > flag or not?
> >
> > grep can do that quite efficiently.
>
> you would still have thousands of descriptions, a lot of them redundand,
> as a big pile. There would be NO advantage doing this. Instead of a short
> explanation, you would get tons of useless text...

I agree here; what I'd like to see is just a bit more thought given to 
use.desc, to offer a hint to the growing user as to what to expect to 
happen. A simple G or L flag would go a long way towards this, but it would 
be more helpful to rewrite most of the descriptions with the user's point 
of view in mind. In particular, "Adds support for foo" should be expunged 
entirely. IMHO.

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



  reply	other threads:[~2006-08-13  8:50 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
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 [this message]
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=200608130948.53413.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