| 1 |
On Wed, Feb 09, 2022 at 06:09:55PM +0100, Michał Górny wrote: |
| 2 |
|
| 3 |
*snip* |
| 4 |
|
| 5 |
> This would: |
| 6 |
> |
| 7 |
> 1) break Gentoo installations behind restrictive firewalls, |
| 8 |
|
| 9 |
Maybe, maybe not. If the go module cache is populated on the firewalled |
| 10 |
system ahead of time things would still work. could emerge -f handle |
| 11 |
this? |
| 12 |
|
| 13 |
> 2) make parallel fetching much harder, |
| 14 |
|
| 15 |
I do not have any comments on this. |
| 16 |
|
| 17 |
> 3) would require custom implementations to support caching |
| 18 |
> and mirroring, |
| 19 |
|
| 20 |
Go already handles both of these with the go proxy mirrors and the |
| 21 |
GOMODCACHE environment variable. |
| 22 |
We could, in the go-module eclass, point GOMODCACHE to for example |
| 23 |
<distdir>/go-mod. |
| 24 |
|
| 25 |
> 4) will eventually lead to ebuilds fetching and using unverified data. |
| 26 |
|
| 27 |
Not for go at least. |
| 28 |
|
| 29 |
https://go.dev/ref/mod#authenticating |
| 30 |
|
| 31 |
William |
Archives