From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] rfc: go 1.13 and go modules
Date: Mon, 9 Sep 2019 14:54:51 -0400 [thread overview]
Message-ID: <8e65e3de-216a-8709-f882-51d95853df0b@gentoo.org> (raw)
In-Reply-To: <fc5c0c92-2a01-599f-aa96-798671533f4f@gentoo.org>
On 9/9/19 2:19 PM, Zac Medico wrote:
> On 9/9/19 10:34 AM, William Hubbs wrote:
>
>> There is another option I want to try which is adding "go mod vendor" to
>> src_unpack for go packages.
>
> If you do that then it will violate FEATURES=network-sandbox (default)
> unless you also do PROPERTIES+=" live".
>
> We could add a separate PROPERTIES value for this, I've suggested it
> before but both Michał Górny and Ulrich Mueller were against it:
>
This is the precisely what FEATURES=network-sandbox exists to prevent.
Bundling dependencies, hitting the network, shelling out to a
language-specific package manager, depending on specific upstream
commits, and sidestepping existing QA mechanisms to make this all
possible... it's bad idea bingo.
next prev parent reply other threads:[~2019-09-09 18:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-09 17:34 [gentoo-dev] rfc: go 1.13 and go modules William Hubbs
2019-09-09 18:19 ` Zac Medico
2019-09-09 18:41 ` William Hubbs
2019-09-09 19:00 ` Michał Górny
2019-09-09 22:10 ` William Hubbs
2019-09-09 22:25 ` Alec Warner
2019-09-09 18:54 ` Michael Orlitzky [this message]
2019-09-09 19:04 ` William Hubbs
2019-09-09 19:00 ` Ulrich Mueller
2019-09-09 20:35 ` Kent Fredric
2019-09-09 21:46 ` William Hubbs
2019-09-09 22:57 ` Georgy Yakovlev
2019-09-09 23:21 ` William Hubbs
2019-09-10 18:31 ` William Hubbs
2019-09-10 18:58 ` Kent Fredric
2019-09-10 1:15 ` Kent Fredric
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=8e65e3de-216a-8709-f882-51d95853df0b@gentoo.org \
--to=mjo@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