From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-desktop@lists.gentoo.org
Cc: gentoo-dev@lists.gentoo.org
Subject: [gentoo-desktop] Re: [RFC] Splitting desktop profile to KDE and GNOME
Date: Mon, 26 Oct 2009 21:39:40 +0000 (UTC) [thread overview]
Message-ID: <pan.2009.10.26.21.39.39@cox.net> (raw)
In-Reply-To: 200910262140.17777.reavertm@gmail.com
Maciej Mrozowski posted on Mon, 26 Oct 2009 21:40:17 +0100 as excerpted:
> And I fail to see *any* point in forcing users to learn Gentoo internals
> (sic! like USE flags). What else? Ebuild syntax so that they're able to
> get to know what particular global USE flag is responsible for, when
> someone forgot (or decided not to) describe it in metadata.xml even when
> semantics is different? Maybe I sound too harsh here, but that's because
> I'm not ideologist - I'm practical man.
Actually, yes. Gentoo has never been a hand-holding distribution. We
try to provide documentation and reasonable defaults for any apps the
user chooses to install, and let the user configure what they will.
For some time I've wondered about all those profiles. IMO, for pure/
normal USE flag issues, we don't need profiles. Profiles are for things
such as setting the arch, masking stuff that won't run on that arch,
doing the necessary to make multilib work as appropriate, setting up a
basic "system" set of packages, etc.
After that, it's upto[1] the user. USE flags are documented in the
handbook, and a major defining part of what makes Gentoo, Gentoo. If
they can't even manage to learn USE flag basics, honestly, they'd be
better off with a different distribution, probably something that does a
bit more hand-holding, like Ubuntu, because they're going thru a whole
lot of additional hassle compiling stuff, etc, for very little payoff in
practical terms, because they simply aren't using Gentoo as it was
designed to be used.
So IMO, few if any USE flags should be set in the profiles. That is, or
should be, upto the user to decide. In general, if a USE flag is not set
in a user's make.conf, it shouldn't be on, with few exceptions definitely
not at the system level, and with some exceptions, not at the individual
ebuild/pkg level either.
---
[1] "Upto": Yeah, I know, but Wictionary already defines it as a "common
misspelling", so make it even more common and eventually it'll no longer
be a misspelling but considered normal and correct usage, just as into is
no longer a misspelling but normal and correct usage.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2009-10-26 21:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-24 13:42 [gentoo-desktop] [RFC] Splitting desktop profile to KDE and GNOME Maciej Mrozowski
[not found] ` <4AE30863.1060007@gentoo.org>
2009-10-24 14:39 ` [gentoo-desktop] Re: [gentoo-dev] " Maciej Mrozowski
2009-10-24 17:30 ` [gentoo-desktop] " Dale
2009-10-26 11:06 ` [gentoo-desktop] Re: [gentoo-dev] " AllenJB
[not found] ` <4AE6012C.6010307@gentoo.org>
2009-10-26 20:40 ` Maciej Mrozowski
2009-10-26 21:16 ` Sebastian Beßler
2009-10-26 21:39 ` Duncan [this message]
2010-01-22 16:15 ` [gentoo-desktop] " Ben de Groot
2010-02-25 22:44 ` 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=pan.2009.10.26.21.39.39@cox.net \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-desktop@lists.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