public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Zac Medico <zmedico@gentoo.org>
To: gentoo-dev@lists.gentoo.org, Kent Fredric <kentnl@gentoo.org>
Subject: Re: [gentoo-dev] [RFC] Disable --autounmask auto-unmasking keywords / masks by default
Date: Wed, 9 Oct 2019 19:45:34 -0700	[thread overview]
Message-ID: <fd2ed6e8-6030-59f8-fe60-aba4def8a675@gentoo.org> (raw)
In-Reply-To: <20191010125323.6acc64f5@katipo2.lan>


[-- Attachment #1.1: Type: text/plain, Size: 1758 bytes --]

On 10/9/19 4:53 PM, Kent Fredric wrote:
> One of the recurring problems we face in #gentoo is end users coming
> to us with confusing problems, and their problems are exacerbated
> because their default workflow ended up with them unmasking some **
> version of perl.
> 
> There is already a bug for this behaviour [1], and comments say that
> portage doing this is "a bug", but the situations which it occurs in
> are hard to diagnose what the "real problem" is.
> 
> Much of the time, what has occurred is there was some other problem,
> and portage bodged its way around the real problem by choosing a
> solution that should be considered unacceptable, instead of presenting
> the real problem.
> 
> Some of the time, the cause is as simple as a single package being
> installed that isn't in the @world dependency graph any more, which is
> tripping up portage slot-rebuild behaviour.
> 
> In practice, what this currently means is that stable users end up
> installing *developmental/experimental* packages that exist only for
> experts and gentoo maintainers, and this is an unacceptable resolution.
> 
> If this behaviour was being triggered by anything other than portage's
> dependency resolver failing, it would be considered a serious QA
> violation.
> 
> Its understood that portage maintainers want to "fix" this behaviour so
> the problem doesn't occur, but until that can be done, the present
> default behaviour is actively harmful, and I suggest it be disabled by
> default until it can be guaranteed to give the right results.
> 
> 1: https://bugs.gentoo.org/658648
> 

I'd prefer to disable --autounmask by default and include warnings about
harmful behavior in the documentation.
-- 
Thanks,
Zac


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 981 bytes --]

  reply	other threads:[~2019-10-10  2:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-09 23:53 [gentoo-dev] [RFC] Disable --autounmask auto-unmasking keywords / masks by default Kent Fredric
2019-10-10  2:45 ` Zac Medico [this message]
2019-10-10  2:57   ` Kent Fredric
2019-10-10  3:35     ` Michael Everitt
2019-10-10  3:39       ` Kent Fredric
2019-10-10  8:09     ` Zac Medico

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=fd2ed6e8-6030-59f8-fe60-aba4def8a675@gentoo.org \
    --to=zmedico@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=kentnl@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