| 1 |
On Mon, 9 Sep 2019 16:46:16 -0500 |
| 2 |
William Hubbs <williamh@g.o> wrote: |
| 3 |
|
| 4 |
> will list the dependencies of a module, but that doesn't look like it |
| 5 |
> can be translated into src_uri format. |
| 6 |
|
| 7 |
If you use the mirror as mentioned in https://blog.golang.org/module-mirror-launch |
| 8 |
|
| 9 |
Then you should be able to do it in a straight-forward way. |
| 10 |
|
| 11 |
You could even encode the dependencies in a bash array like: |
| 12 |
|
| 13 |
GO_MODULES=( |
| 14 |
Foo@v0.2.3 |
| 15 |
) |
| 16 |
|
| 17 |
Which would be expanded by the ebuild during "use go" or whatever, to |
| 18 |
|
| 19 |
https://proxy.golang.org/${PN}/foo/@v/v0.2.3.zip -> ${PN}-foo-v0.2.3.zip |
| 20 |
|
| 21 |
Or something like that. |
Archives