From: Tanstaafl <tanstaafl@libertytrek.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] emerge -e system - output info/errors to log
Date: Wed, 28 Apr 2010 13:38:58 -0400 [thread overview]
Message-ID: <4BD872B2.2020400@libertytrek.org> (raw)
In-Reply-To: <201004181956.46928.alan.mckinnon@gmail.com>
On 2010-04-18 1:56 PM, Alan McKinnon wrote:
> Understand what the gcc upgrade guide is:
>
> a quick simple guide for user who don't know tool chains inside out, that give
> the minimal sequence of commands that is GUARANTEED to NOT leave the user in
> the lurch. It's not the minimum possible sequence of commands to do the
> upgrade, because most users don't know how to tell the difference. Here's the
> logic:
>
> "If we imply that you should merge -e world with a gcc upgrade, my inbox will
> not fill with bugs from users who don't know the inner guts of the toolchain".
>
> The Guide is not the best possible guide that can be. It is the guide that
> causes the least support questions from users.
This is the second time that someone has said something like this with
respect to the official Gentoo Guides (the other was the kernel upgrade
guide, and its recommendation to use ''make menuconfig instead of 'make
oldconfig')...
It would be nice if there were a formal/official place to find 'Advanced
User Guides'... ;)
--
Charles
next prev parent reply other threads:[~2010-04-28 17:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-18 15:38 [gentoo-user] emerge -e system - output info/errors to log Tanstaafl
2010-04-18 15:41 ` Tanstaafl
2010-04-18 17:40 ` Dale
2010-04-18 17:05 ` Alan McKinnon
2010-04-18 17:37 ` Tanstaafl
2010-04-18 17:56 ` Alan McKinnon
2010-04-18 18:10 ` Neil Bothwick
2010-04-28 17:38 ` Tanstaafl [this message]
2010-04-28 21:02 ` Dale
2010-04-18 18:05 ` Neil Bothwick
2010-04-28 17:47 ` Tanstaafl
2010-05-06 13:04 ` Tanstaafl
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=4BD872B2.2020400@libertytrek.org \
--to=tanstaafl@libertytrek.org \
--cc=gentoo-user@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