| 1 |
On Mon, 2019-09-09 at 13:41 -0500, William Hubbs wrote: |
| 2 |
> On Mon, Sep 09, 2019 at 11:19:02AM -0700, Zac Medico wrote: |
| 3 |
> > On 9/9/19 10:34 AM, William Hubbs wrote: |
| 4 |
> > |
| 5 |
> > > There is another option I want to try which is adding "go mod vendor" to |
| 6 |
> > > src_unpack for go packages. |
| 7 |
> > |
| 8 |
> > If you do that then it will violate FEATURES=network-sandbox (default) |
| 9 |
> > unless you also do PROPERTIES+=" live". |
| 10 |
> > |
| 11 |
> > We could add a separate PROPERTIES value for this, I've suggested it |
| 12 |
> > before but both Michał Górny and Ulrich Mueller were against it: |
| 13 |
> > |
| 14 |
> > https://archives.gentoo.org/gentoo-portage-dev/message/6d696661b29b6e2b8c82061e89e4718f |
| 15 |
> |
| 16 |
> If checksum verification is the concern, Go 1.13 also has this: |
| 17 |
> |
| 18 |
> https://blog.golang.org/module-mirror-launch |
| 19 |
> |
| 20 |
> Thoughts? Does this make the case for a property for these kinds of |
| 21 |
> ebuilds? |
| 22 |
> |
| 23 |
|
| 24 |
Checksum verification is only one of the problems. The other one is |
| 25 |
that it won't work if you don't have permanent Internet access or are |
| 26 |
using strong firewalling. |
| 27 |
|
| 28 |
Ebuilds are using a single fetching mechanisms so that people can adjust |
| 29 |
it as necessary for their setup. It's not fine to try to silently work |
| 30 |
around that and access Internet. |
| 31 |
|
| 32 |
-- |
| 33 |
Best regards, |
| 34 |
Michał Górny |
Archives