From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] New Portage fork: sys-apps/portage-mgorny
Date: Sat, 24 Mar 2018 08:54:25 -0400 [thread overview]
Message-ID: <CAGfcS_=Pfs9FRsityrfFkkaZGeGGgHbD-seEcjJhj8A+0P5wAw@mail.gmail.com> (raw)
In-Reply-To: <20180324220114.748273c5@katipo2.lan>
On Sat, Mar 24, 2018 at 5:01 AM, Kent Fredric <kentnl@gentoo.org> wrote:
> On Sat, 24 Mar 2018 09:02:20 +0100
> Michał Górny <mgorny@gentoo.org> wrote:
>
>> ...except that it is also used to say 'this is experimental version,
>> unmask at will' and Portage wants to unmask stuff for you anyway. Well,
>> I mean the default configuration of Portage, not mine.
>
> Yeah, that default I find incredibly stupid tbh.
>
> Auto-unmask use works nicely. Autounmask for package.mask and
> accept_keywords is just madness I'd love to see stopped.
>
It can be useful, though obviously I review what is proposed before
merging the config changes.
I wouldn't put masks and keywords in the same bucket. A mask
typically means that something is known to cause problems, while
missing keywords typically just means that it isn't known to work yet.
People running mixed-keywords will find themselves accepting keywords
a fair bit.
--
Rich
next prev parent reply other threads:[~2018-03-24 12:54 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 [this message]
2018-03-24 18:27 ` Zac Medico
2018-03-24 20:33 ` Kent Fredric
2018-03-24 20:44 ` Zac Medico
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='CAGfcS_=Pfs9FRsityrfFkkaZGeGGgHbD-seEcjJhj8A+0P5wAw@mail.gmail.com' \
--to=rich0@gentoo.org \
--cc=gentoo-dev@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