public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Dawid Węgliński" <cla@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Splitting desktop profile to KDE and GNOME
Date: Tue, 27 Oct 2009 01:34:55 +0100	[thread overview]
Message-ID: <200910270134.55224.cla@gentoo.org> (raw)
In-Reply-To: <op.u2fkqoiragyv58@zeerak>

On Tuesday 27 October 2009 00:26:38 Zeerak Waseem wrote:
> But instead of just giving the user the answer, wouldn't it be more
> appropriate, as far as understanding useflags and their uses goes, to give
> users lists of useflags and what they do. Ie a list of base use flags for
> say, kde, and also what basic useflags to disable, and a suggestion to
> read the descriptions of the useflags to add what's necessary. As the
> handbook currently does. I think with the documentation, one should have
> enough information to assess what useflags are desired for one's system.
> And then I'd suggest looking at the packages and the need for various use
> flags individually, if you want to. But the documentation provides basic
> useflags for running your system.
> But again, this is just my take on it :-)
> 

No. Handbook doesn't provide information on every useflag. For this you have 
use{.local.,.}desc in PORTDIR/profiles/. And again, if you missread my previous 
post - there's no way to standarize *every* useflag and tell user "flag foo does 
bar". It's developer who should decide on behalf of user what's the best 
configuration. And user has always choice to disable some useflags and create 
his own configuration for his requirements.

-- 
Cheers
Dawid Węgliński



  reply	other threads:[~2009-10-26 23:36 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-24 13:42 [gentoo-dev] [RFC] Splitting desktop profile to KDE and GNOME Maciej Mrozowski
2009-10-24 13:51 ` Nirbheek Chauhan
2009-10-24 15:32   ` Petteri Räty
2009-10-24 14:00 ` Jeremy Olexa
2009-10-24 14:39   ` Maciej Mrozowski
2009-10-26  1:10   ` Jeroen Roovers
2009-10-25  7:41 ` Jesús Guerrero
2009-10-26 23:47   ` Mike Frysinger
2009-10-26 11:06 ` AllenJB
2009-10-26 11:11   ` Samuli Suominen
2009-10-26 12:43     ` AllenJB
2009-10-26 18:28     ` Joshua Saddler
2009-10-26 19:42   ` Zeerak Waseem
2009-10-26 19:52     ` Alex Alexander
2009-10-26 20:21       ` Dale
2009-10-26 23:28       ` Jesús Guerrero
2009-10-26 14:58 ` Robert Buchholz
2009-10-26 20:06 ` Rémi Cardona
2009-10-26 20:40   ` Maciej Mrozowski
2009-10-26 21:21     ` Josh Sled
2009-10-26 21:39     ` [gentoo-dev] " Duncan
2009-10-26 21:58       ` Richard Freeman
2009-10-26 22:17         ` Rémi Cardona
2009-10-27 16:07           ` Richard Freeman
2009-10-27 16:54             ` William Hubbs
2009-10-27 17:43               ` Thomas Sachau
2009-10-27 17:59                 ` William Hubbs
2009-10-27 18:07                   ` Nirbheek Chauhan
2009-10-27 18:44                     ` William Hubbs
2009-10-26 22:51         ` Zeerak Waseem
2009-10-27  0:08   ` [gentoo-dev] " Dawid Węgliński
2009-10-26 23:26     ` Zeerak Waseem
2009-10-27  0:34       ` Dawid Węgliński [this message]
2009-10-27  0:39         ` Dawid Węgliński
     [not found] ` <e117dbb91001220815r7f55508bxfffd8b954a677d43@mail.gmail.com>
2010-02-25 22:44   ` [gentoo-dev] Re: [gentoo-desktop] " Theo Chatzimichos

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=200910270134.55224.cla@gentoo.org \
    --to=cla@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