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] New Portage fork: sys-apps/portage-mgorny
Date: Sat, 24 Mar 2018 13:44:49 -0700	[thread overview]
Message-ID: <25def267-c246-7c47-48f9-d889c9087ef2@gentoo.org> (raw)
In-Reply-To: <20180325093340.4237c829@katipo2.lan>


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

On 03/24/2018 01:33 PM, Kent Fredric wrote:
> On Sat, 24 Mar 2018 11:27:20 -0700
> Zac Medico <zmedico@gentoo.org> wrote:
> 
>> The defaults certainly do not work perfectly in all situations. However,
>> there are a vast number of situations where using --autounmask-continue
>> will make appropriate package.mask changes without the need for any user
>> intervention.
> 
> Its really handy for use flags.
> 
> Its really handy for mixed arch/~arch where it promotes arch to ~arch as needed.
> 
> Its really really bad however to have a default of accepting ** and
> package.unmask as a primary go-to solution.

That only happens when dependency satisfaction fails by normal means.

> That default gets people using broken openssl and experimental packages
> blindly without them ever having intended on getting into experimental
> waters.

If people can't be bothered to understand the meaning of package.mask
and keywords changes, should they really be using Gentoo?
-- 
Thanks,
Zac


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

  reply	other threads:[~2018-03-24 20:44 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-22 19:03 [gentoo-dev] New Portage fork: sys-apps/portage-mgorny Michał Górny
2018-03-22 20:17 ` James Le Cuirot
2018-03-22 20:27   ` Michał Górny
2018-03-22 20:31   ` Zac Medico
2018-03-23  1:01   ` Herb Miller Jr.
2018-03-23  8:28     ` Michał Górny
2018-03-22 21:47 ` Consus
2018-03-22 22:06   ` Michał Górny
2018-03-22 22:52     ` Geaaru
2018-03-22 23:22       ` Zac Medico
2018-03-23  8:31       ` Michał Górny
2018-03-23  9:48       ` Ulrich Mueller
2018-03-23 10:18         ` Francesco Riosa
2018-03-23 10:38           ` Franz Fellner
2018-03-23 10:53           ` Ulrich Mueller
2018-03-24  7:02             ` Kent Fredric
2018-03-24  8:02               ` Michał Górny
2018-03-24  9:01                 ` Kent Fredric
2018-03-24 12:54                   ` Rich Freeman
2018-03-24 18:27                   ` Zac Medico
2018-03-24 20:33                     ` Kent Fredric
2018-03-24 20:44                       ` Zac Medico [this message]
2018-03-25  2:26                         ` Kent Fredric
2018-03-25  4:43                           ` Zac Medico
2018-03-25  9:02                             ` Kent Fredric
2018-03-26  7:48                               ` Zac Medico
2018-03-23 10:38         ` Roy Bamford
2018-03-23 10:59           ` Ulrich Mueller
2018-03-23 13:27             ` Rich Freeman
2018-03-23 14:25               ` Arve Barsnes
2018-03-23 16:20                 ` Geaaru
2018-03-23 16:23                 ` Patrick Steinhardt
2018-03-23 20:16                   ` Georgy Yakovlev
2018-03-23 17:44               ` Patrick McLean
2018-03-26 16:48                 ` Thomas Deutschmann
2018-03-26 18:36                   ` Zac Medico
2018-03-25 10:13       ` Vadim A. Misbakh-Soloviov
2018-03-28  4:42         ` [gentoo-dev] " Duncan
2018-03-23 11:25     ` [gentoo-dev] " Consus
2018-05-19 15:53 ` Consus
2018-05-22 20:35   ` Michał Górny
2018-05-28  2:45     ` Richard Yao

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=25def267-c246-7c47-48f9-d889c9087ef2@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