From: Kent Fredric <kentnl@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Begin a dev-libs/nodejs category?
Date: Wed, 21 Mar 2018 20:33:35 +1300 [thread overview]
Message-ID: <20180321203335.17c9a2f5@katipo2.lan> (raw)
In-Reply-To: <BLUPR17MB0273D5510468C40F430CAC1DD9AA0@BLUPR17MB0273.namprd17.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 785 bytes --]
On Wed, 21 Mar 2018 01:44:11 +0000
Herb Miller Jr. <herb@hlmjr.com> wrote:
> If I am, then yes, some kind of automation
> would be the only sane way to keep up
In my experience you can't *really* rely on automation 100% for this
sort of thing. Not while achieving quality results.
Its viable for an overlay where there's no expectations of quality, but
for the main tree, I find you want to have a human san-check everything
and manually vet each upstream version for "anomalous things".
Automation is good at handling the "known predictable" cases, humans
are better at detecting "huh, that's weird, why did they do that?"
Because you absolutely want to know if upstream added some stupid
change that is harmful to Gentoo users before you blindly replicate it.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-03-21 7:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 11:50 [gentoo-dev] [RFC] Begin a dev-libs/nodejs category? Herb Miller Jr.
2018-03-20 18:34 ` Michał Górny
2018-03-20 19:43 ` Herb Miller Jr.
2018-03-20 18:48 ` Michael Orlitzky
2018-03-20 20:14 ` Herb Miller Jr.
2018-03-20 20:44 ` Michael Orlitzky
2018-03-21 1:27 ` Kent Fredric
2018-03-21 1:36 ` M. J. Everitt
2018-03-20 23:50 ` Benda Xu
2018-03-21 1:44 ` Herb Miller Jr.
2018-03-21 7:33 ` Kent Fredric [this message]
2018-03-21 12:22 ` Herb Miller Jr.
2018-03-21 10:07 ` X dej
2018-03-21 12:15 ` [gentoo-dev] Pypi generator (Was: [RFC] Begin a dev-libs/nodejs category?) Benda Xu
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=20180321203335.17c9a2f5@katipo2.lan \
--to=kentnl@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