From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: emerge -C eselect-python disaster
Date: Tue, 26 Jan 2010 01:26:53 +0000 (UTC) [thread overview]
Message-ID: <pan.2010.01.26.01.26.54@cox.net> (raw)
In-Reply-To: 4B5DC16E.6090200@gmail.com
Dale posted on Mon, 25 Jan 2010 10:06:06 -0600 as excerpted:
> I am subscribed to -user as well. I been using Gentoo since the 1.4
> days. This is about improving portage which is a good thing to talk
> about here. The devs do it, not the user. ;-) Also, I already know
> how to use portage pretty good. I'm not asking for support just trying
> to improve things.
Do note that there's a portage-specific list as well. IDR what the name
is but on gmane (where I follow it) it's the
gmane.linux.gentoo.portage.devel newsgroup. It's not a user list either,
but they're reasonably friendly and it wouldn't be bothering the non-
portage devs that way.
As for this, I say let it be (except for possibly making -C output a
bigger warning in general). The documentation is pretty clear, and Gentoo
never has been about hand-holding. If a user can't read the documentation
and thus asks to screw themselves, Gentoo provides the tools to do it --
and they're POWER tools, too! =:^) I don't see that changing and don't
believe it should. There's other distributions out there for users who
want or need a namby-pamby baby-sat hand-held version. Gentoo is not and
never has been the right choice for them, and I don't believe we should be
trying to make it so. (That said, a warning on -C similar to that on -c,
might be wise, but that's an implementation detail the discussion of which
doesn't belong here.)
--
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:[~2010-01-26 2:12 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-24 5:12 [gentoo-dev] emerge -C eselect-python disaster Benny Pedersen
2010-01-24 9:03 ` Ulrich Mueller
2010-01-24 9:40 ` Petteri Räty
2010-01-24 11:07 ` Petteri Räty
2010-01-24 13:02 ` Ben de Groot
2010-01-24 16:53 ` Petteri Räty
2010-01-24 18:20 ` Ben de Groot
2010-01-24 20:19 ` Petteri Räty
2010-01-25 0:02 ` Dale
2010-01-25 1:53 ` Jacob Godserv
2010-01-25 2:28 ` Dale
2010-01-25 9:26 ` Petteri Räty
2010-01-25 11:02 ` Dale
2010-01-25 11:30 ` Petteri Räty
2010-01-25 11:32 ` Petteri Räty
2010-01-25 16:06 ` Dale
2010-01-25 17:04 ` Petteri Räty
2010-01-26 1:26 ` Duncan [this message]
2010-01-25 16:20 ` Jacob Godserv
2010-01-25 17:02 ` Petteri Räty
2010-01-25 17:07 ` Dale
2010-01-25 18:01 ` Petteri Räty
2010-01-25 16:21 ` Patrick Nagel
2010-01-25 2:22 ` Richard Freeman
2010-01-25 5:03 ` Dale
2010-01-25 9:25 ` Petteri Räty
2010-01-24 23:06 ` Richard Freeman
2010-01-24 11:29 ` Arttu V.
2010-01-24 13:03 ` Dale
2010-01-24 21:15 ` Mike Frysinger
2010-01-25 11:10 ` Arfrever Frehtes Taifersar Arahesis
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.2010.01.26.01.26.54@cox.net \
--to=1i5t5.duncan@cox.net \
--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