From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: zmedico@gentoo.org, ulm@gentoo.org
Subject: Re: [gentoo-dev] rfc: go 1.13 and go modules
Date: Mon, 09 Sep 2019 21:00:31 +0200 [thread overview]
Message-ID: <d93fa8c137ded2527deab6d093b4cb8b9a435875.camel@gentoo.org> (raw)
In-Reply-To: <20190909184107.GA31538@whubbs1.dev.av1.gaikai.org>
[-- Attachment #1: Type: text/plain, Size: 1272 bytes --]
On Mon, 2019-09-09 at 13:41 -0500, William Hubbs wrote:
> On Mon, Sep 09, 2019 at 11:19:02AM -0700, 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:
> >
> > https://archives.gentoo.org/gentoo-portage-dev/message/6d696661b29b6e2b8c82061e89e4718f
>
> If checksum verification is the concern, Go 1.13 also has this:
>
> https://blog.golang.org/module-mirror-launch
>
> Thoughts? Does this make the case for a property for these kinds of
> ebuilds?
>
Checksum verification is only one of the problems. The other one is
that it won't work if you don't have permanent Internet access or are
using strong firewalling.
Ebuilds are using a single fetching mechanisms so that people can adjust
it as necessary for their setup. It's not fine to try to silently work
around that and access Internet.
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
next prev parent reply other threads:[~2019-09-09 19:00 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 [this message]
2019-09-09 22:10 ` William Hubbs
2019-09-09 22:25 ` Alec Warner
2019-09-09 18:54 ` Michael Orlitzky
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=d93fa8c137ded2527deab6d093b4cb8b9a435875.camel@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=ulm@gentoo.org \
--cc=zmedico@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