public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
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 07:46:10 +0000 (UTC)	[thread overview]
Message-ID: <slrnl7jsuc.ucd.vaeth@lounge.imp.fu-berlin.de> (raw)
In-Reply-To: 52794E07.80008@gmail.com

Alan McKinnon <alan.mckinnon@gmail.com> wrote:
>
> You don't have to keep explaining subslots to me

But not every reader knows the details - this is not a private
conversation.

> What I have maintained all along is that I don't see the solution as
> tested to be production-ready

It has been in ~arch for many months, and now it is becoming stable.
This is how testing works in gentoo.
As I tried to explain, even if devs do it wrong, there is not much
harm which can happen except for useless rebuilds or that the
advantage of subslots is missed by mistake.

In practice, it turns out that the portage error messages tend to
confuse users more now: The reason being that, although portage
would be able to resolve subslot dependencies automatically,
it does not show the resolved ones if it breaks before because of
an error, and so users see a lot of errors which actually are none
but occur only as a side effect of a completely different problem.
Although this behavior of portage happens not only for subslots,
the number of "false positives" has increased due to subslots.
This leads to the wrong perceiption which one can see in the forums.
  But misleading error messages due to non-finished resolving
were a problem which existed also before in portage and which
should be attacked anyway, if it can be.



  reply	other threads:[~2013-11-06  7:46 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
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 [this message]
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=slrnl7jsuc.ucd.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