From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] And so the emerge spake: Let there be conflicts...and see, everything was chaos and sin...
Date: Sun, 26 Apr 2015 23:06:02 +0100 [thread overview]
Message-ID: <20150426230602.1e3e215e@hactar.digimed.co.uk> (raw)
In-Reply-To: <20150426212847.GF1067@ca.inter.net>
[-- Attachment #1: Type: text/plain, Size: 1274 bytes --]
On Sun, 26 Apr 2015 17:28:47 -0400, Philip Webb wrote:
> > More seriously, once you start working on (3), you'll realize
> > that just because the error msgs suck doesn't mean you can make them
> > better.
>
> If they "suck", they're not worth issuing, are they ?
Of course they are, obtuse error messages are better than none.
However, one of the problems with portage's output, and it threw a few
people with the OP's original question, is that portage makes no clear
distinction between error and informational messages. The, not
unreasonable, assumption is that when portage spews out several lines of
information about not being able to install a package because of version
requirements of other packages an error has occurred. In many cases, like
this one, that is simply not the case. Even some colour highlighting of
messages would go a fair way to improving the readability of portage's
output.
However, I am prepared to accept that changes in this department are not
trivial and if no one else is prepared to do something, I can either fix
it myself or accept it as it is. I've been using Gentoo for too long to
be entitled to a refund for what I paid for it.
--
Neil Bothwick
Pedestrians come in two types: Quick or Dead.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2015-04-26 22:06 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-25 16:07 [gentoo-user] And so the emerge spake: Let there be conflicts...and see, everything was chaos and sin Meino.Cramer
2015-04-25 20:15 ` Daniel Frey
2015-04-26 2:06 ` Meino.Cramer
2015-04-26 7:38 ` Alan McKinnon
2015-04-26 14:16 ` Daniel Frey
2015-04-26 6:49 ` [gentoo-user] " Martin Vaeth
2015-04-26 7:32 ` Meino.Cramer
2015-04-26 13:13 ` Martin Vaeth
2015-04-26 13:30 ` Meino.Cramer
2015-04-26 8:19 ` Neil Bothwick
2015-04-26 13:08 ` Martin Vaeth
2015-04-26 7:35 ` [gentoo-user] " Alan McKinnon
2015-04-26 7:57 ` Meino.Cramer
2015-04-26 11:30 ` Alan McKinnon
2015-04-26 11:45 ` Meino.Cramer
2015-04-26 8:17 ` Neil Bothwick
2015-04-26 13:49 ` Alan McKinnon
2015-04-26 15:14 ` Peter Humphrey
2015-04-26 16:07 ` [gentoo-user] " walt
2015-04-26 17:17 ` [gentoo-user] " Neil Bothwick
2015-04-26 19:17 ` Philip Webb
2015-04-26 20:23 ` Michael Orlitzky
2015-04-26 21:28 ` Philip Webb
2015-04-26 22:06 ` Neil Bothwick [this message]
2015-04-26 22:23 ` Michael Orlitzky
2015-04-27 5:47 ` Alan McKinnon
2015-04-28 14:11 ` Dale
2015-04-28 16:34 ` Philip Webb
2015-04-27 5:40 ` Alan McKinnon
2015-04-27 7:30 ` [gentoo-user] " Martin Vaeth
2015-04-26 20:48 ` james
2015-04-27 20:11 ` Michael Orlitzky
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=20150426230602.1e3e215e@hactar.digimed.co.uk \
--to=neil@digimed.co.uk \
--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