public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Jesús Guerrero" <i92guboj@terra.es>
To: <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] [RFC] Splitting desktop profile to KDE and GNOME
Date: Tue, 27 Oct 2009 00:28:15 +0100	[thread overview]
Message-ID: <86cdfc0186b58a62f07bc32572020e16@localhost> (raw)
In-Reply-To: <225000070910261252t16155c78s5461c1f13fff406d@mail.gmail.com>

On Mon, 26 Oct 2009 21:52:04 +0200, Alex Alexander <wired@gentoo.org>
wrote:
> On Mon, Oct 26, 2009 at 21:42, Zeerak Waseem <zeerak.w@gmail.com> wrote:
>> having to choose a profile, gives less time for the wavering user
> 
> Why all the fuss? No-one said we're removing the plain "desktop"
> profile, we're simply adding *more* options.
> 
> If you want generic DE options pre-enabled, choose the desktop profile.
> If you *know* you only need KDE as your DE, choose KDE,
> If you *know* you only need GNOME as your DE, choose GNOME,
> If you need both or can't decide, either choose Desktop and add the
> USE flags yourself or use both profiles together.
> 
> Beats enabling default USE flags without asking you :)

My personal definition of bloat: "to add complexity for no real gain on
features". Adding a profile just because it's a cool way to do the same
thing that *one* single USE flag can do is a nonsense *to me*.

I am already hearing all the new (and old) users asking what the damn
difference between the flag and the profile is. It's a cool way to create
extra traffic and confusion for absolutely no benefit. But hey, maybe it's
just that my old brain can't cope with the coolness :)
-- 
Jesús Guerrero



  parent reply	other threads:[~2009-10-26 23:28 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 [this message]
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
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=86cdfc0186b58a62f07bc32572020e16@localhost \
    --to=i92guboj@terra.es \
    --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