From: "Zeerak Waseem" <zeerak.w@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [RFC] Splitting desktop profile to KDE and GNOME
Date: Mon, 26 Oct 2009 23:51:25 +0100 [thread overview]
Message-ID: <op.u2fi3zzlagyv58@zeerak> (raw)
In-Reply-To: <4AE61BA1.1030106@gentoo.org>
When it all comes down, I just fail to see how the handbook doesn't
provide the pointers. I've always been about getting my system up and
running, and then learn whatever needs learning, this means that whilst I
didn't have more than a basic knowledge and understanding of useflags when
installing, that knowledge has grown due to necessity of using gentoo to
it's full potential. I think setting up useflags should be left to the
user. A system can be recompiled should the need arise.
The reason I chose gentoo as my distribution was that, it seemed to me
that it gives you a basic knowledge of the system and then encourages to
gain and apply further knowledge according to need.
But again, the handbook gives all the necessary pointers, albeit there can
occur conflicts that are outside of the range of the handbook, but that's
why the forums and the irc channels are there :-)
On Mon, 26 Oct 2009 22:58:57 +0100, Richard Freeman <rich0@gentoo.org>
wrote:
> I don't see why having some nice polished sets of use flags is a bad
> thing. Personally, I find it a pain when I've emerged half of my system
> only to find out I left out some critical use flag (my use flags take up
> several lines now). Sure, leave users a choice, but there is no harm in
> giving them some pointers.
>
> Gentoo should be fully usable in a USE="" state, but that doesn't mean
> that we need to make users start out from this point.
>
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
next prev parent reply other threads:[~2009-10-26 22:51 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 [this message]
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=op.u2fi3zzlagyv58@zeerak \
--to=zeerak.w@gmail.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