e8ffd43a29
This naming scheme seemed weird to me so I went looking around at other Go projects. None of the projects that I found that had multi-arch release binaries used this scheme, instead they just append the variant to arch. Appending the variant to the arch also makes a lot of sense if you think of the naming schme as $binary-$os-$cpu and $cpu=$arch$variant. Keeping arch and variant together as $cpu is also more consistent, and consitency is great :D. Signed-off-by: Manuel Mendez <mmendez@equinix.com> |
||
|---|---|---|
| .. | ||
| docker | ||
| tar | ||
| main.go | ||