From: James Gibson <twistedhammer@subdimension.com>
To: Thomas Beaudry <tmbeaudry@msn.com>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Automatic menus?
Date: Thu, 25 Jul 2002 19:50:50 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0207251932200.2834-100000@camero.fantasia.tld> (raw)
In-Reply-To: <F21y2NRcMs7rLy5TFSJ0000f8a5@hotmail.com>
On Fri, 26 Jul 2002, Thomas Beaudry wrote:
> Maybe I could have phrased that a little better. The message
> I was replying to talked about not wanting it in Gentoo because
> he dislikes it and always shuts it off in Mandrake.
>
> I was just saying that that is selfish, to deny others a feature
> just so he doesn't have to be bothered with a few minutes time
> to get rid of it.
>
> In otherwords, I was responding in the context he created.
I must appologize; In large part my response was targeted at the wording,
even though I was pretty certain that you hadn't meant it that way, and
I'm sorry to have put you between the sights, so to speak.
I've just seen people who honestly felt that they were doing people a
favour by blindly adding new features that are 'opt-out', when the only
real excuse for that model of improvement is to 'make it easier for the
newbies'; a fact which has the inverse effect of making it harder for the
more discerning users. e.g. you _can_ disable the majority of the
automation cruft that SuSE installs without breaking their system, but in
general it is more of a pain in the neck than it is worth.
> Of course if a menu ebuild is implemented, it would be an op-in
> just like every other ebuild under Gentoo. I didn't think it
> was necessary to point out the obvious. Guess I was wrong.
You will have to excuse me.. I've been overlooking the obvious all day
long. I think I need to get some more sleep. =)
--James
next prev parent reply other threads:[~2002-07-26 2:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-26 1:04 [gentoo-dev] Automatic menus? Thomas Beaudry
2002-07-26 2:50 ` James Gibson [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-25 3:11 Thomas Beaudry
2002-07-25 21:15 ` James Gibson
2002-07-25 21:52 ` Jon Nelson
2002-07-26 3:50 ` Felipe Ghellar
2002-07-26 4:47 ` Tom Philbrick
2002-07-26 5:09 ` Felipe Ghellar
2002-07-26 4:23 ` Tom Philbrick
2002-07-24 15:08 Tom Philbrick
2002-07-24 15:14 ` Jon Nelson
2002-07-24 22:46 ` Peter Ruskin
2002-07-24 23:21 ` Grant Goodyear
2002-07-26 12:45 ` Corvus Corax
2002-07-26 13:19 ` Paul de Vrieze
2002-07-26 17:53 ` Tom Philbrick
2002-07-26 18:03 ` Jean-Michel Smith
2002-07-29 17:22 ` Tom Philbrick
2002-07-29 10:05 ` Noah Justin Norris
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=Pine.LNX.4.44.0207251932200.2834-100000@camero.fantasia.tld \
--to=twistedhammer@subdimension.com \
--cc=gentoo-dev@gentoo.org \
--cc=tmbeaudry@msn.com \
/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