| 1 |
On Mon, Mar 07, 2022 at 01:10:46PM +0100, tastytea wrote: |
| 2 |
> On 2022-03-05 16:17-0600 William Hubbs <williamh@g.o> wrote: |
| 3 |
> |
| 4 |
> > +# @CODE |
| 5 |
> > +# |
| 6 |
> > +# $ cd /path/to/project |
| 7 |
> > +# $ GOMODCACHE="${PWD}"/go-mod go mod download -modcacherw |
| 8 |
> > +# $ tar -acf project-1.0-deps.tar.xz go-mod |
| 9 |
> |
| 10 |
> What's the reason to use `go mod download` here and not `go mod |
| 11 |
> vendor`? The former seems to always generate much bigger directories. |
| 12 |
> For www-apps/hugo it is 1.5G vs. 65M and someone on IRC mentioned that |
| 13 |
> for another ebuild it is >600M vs 22M. |
| 14 |
|
| 15 |
You are correct, it does generate bigger directories. "go mod vendor" |
| 16 |
doesn't preserve everything needed to make some builds happen, so I had |
| 17 |
to go with "go mod download". For more info, see the following upstream |
| 18 |
issue (note that several folks have asked for the discussion to be |
| 19 |
restarted; I haven't seen any responses yet). |
| 20 |
|
| 21 |
http://github.com/golang/go/issues/26366 |
| 22 |
|
| 23 |
Thanks, |
| 24 |
|
| 25 |
William |
Archives