From: Martin Vaeth <vaeth@mathematik.uni-wuerzburg.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: do subslots improve user-experience?
Date: Wed, 6 Nov 2013 12:54:27 +0000 (UTC) [thread overview]
Message-ID: <slrnl7kf0e.1dg.vaeth@lounge.imp.fu-berlin.de> (raw)
In-Reply-To: 20131106125035.2ccb756a@marcec
Marc Joliet <marcec@gmx.de> wrote:
>
> One of those questions stands out to me right now: the one on understandable
> error messages. As some recent posts to this ML demonstrate, it seems to
> be one area where portage is visibly falling (staying?) behind right now.
> They remind me of the type of error message gcc/g++ spit out, actually.
In both cases, it is technically very cumbersome to get good
error messages. In fact, it would need alone more work in programming
than to do the actual job (and it would slow down execution time
drastically even if no errors arise).
Concerning portage, the situation is apparently this
(I am guessing this only from the outputs which are posted):
When portage detects that it cannot resolve something after
backtracking, it dies. Then all non-resolved conflicts are
spit out - often these are some that *could* be resolved.
So instead of dying, portage would need to try to continue
to resolve anyway partially as far as it could and only then
die. This would mean that branches cannot be cut, so the runtime
would probably increase tremendously. Moreover, the result might
be even more confusing if there is some strange branch in which
slightly more resolving is possible.
next prev parent reply other threads:[~2013-11-06 12:55 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-02 12:04 [gentoo-user] do subslots improve user-experience? hasufell
2013-11-02 12:31 ` Philip Webb
2013-11-02 13:16 ` Alan McKinnon
2013-11-03 19:07 ` [gentoo-user] " Martin Vaeth
2013-11-03 19:23 ` hasufell
2013-11-04 7:46 ` Martin Vaeth
2013-11-03 19:55 ` Alan McKinnon
2013-11-05 9:52 ` Martin Vaeth
2013-11-05 10:04 ` Peter Humphrey
2013-11-05 10:14 ` Alan McKinnon
2013-11-05 12:11 ` Marc Joliet
2013-11-05 14:44 ` Alan McKinnon
2013-11-05 15:21 ` Bruce Hill
2013-11-05 19:47 ` Alan McKinnon
2013-11-06 11:50 ` Marc Joliet
2013-11-06 12:54 ` Martin Vaeth [this message]
2013-11-06 18:15 ` Alan McKinnon
2013-11-07 6:26 ` Martin Vaeth
2013-11-05 18:06 ` Martin Vaeth
2013-11-05 19:59 ` Alan McKinnon
2013-11-06 7:46 ` Martin Vaeth
2013-11-06 13:11 ` Alan McKinnon
2013-11-07 6:16 ` Martin Vaeth
2013-11-02 15:32 ` [gentoo-user] " Daniel Campbell
2013-11-02 16:14 ` Dustin C. Hatch
2013-11-02 17:07 ` Daniel Frey
2013-11-02 19:56 ` Volker Armin Hemmann
2013-11-02 20:33 ` thegeezer
2013-11-02 21:26 ` Neil Bothwick
2013-11-03 0:38 ` [gentoo-user] " walt
2013-11-03 10:16 ` Neil Bothwick
2013-11-05 13:29 ` [gentoo-user] " Bruce Hill
2013-11-05 14:29 ` Bruce Hill
2013-11-05 21:28 ` Neil Bothwick
2013-11-05 21:38 ` Bruce Hill
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=slrnl7kf0e.1dg.vaeth@lounge.imp.fu-berlin.de \
--to=vaeth@mathematik.uni-wuerzburg.de \
--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