FR: Release tags for the synthetic Go branch

[imjasonh]

trafficstars

Description

I'd like to depend on the synthetic Go branch, but it seems to only track the head of the main branch, and doesn't have any tags corresponding to real release tags.

Is this feature related to a specific bug?

Nope.

I'm having some difficulty building the project with Bazel, and I'd love to be able to just use Go instead.

Do you have a specific solution in mind?

Something like synthetic tags for go-release-20240617.0 corresponding to release-20240617.0, and so on.

[milantracy]

Which error/failure did you see when you build the project with bazel ?

[imjasonh]

I posted yesterday on the gitter:

Hey all, I have a question about building gvisor from source using bazel. I'm trying to build for only one platform, not using the Docker builder container, and it's failing for me because /usr/bin/x86_64-linux-gnu-gcc isn't found on aarch64 (and vice versa). I'm running bazel build --config=aarch64 //runsc but that doesn't seem to be enough.

It's probably not insurmountable, but in general building with Go seems a lot easier for me than building with Bazel, except that I can't pin to a release the same way.

[kevinGC]

A couple things:

1. While we don't have tags in the go branch, you can use pseudo versions to pin to a particular commit.
2. The Go branch is great for using gVisor as a dependency, but if you're actually working on or building runsc, bazel is the way to do it.
3. That linux-gnu-gcc thing is a frustrating error -- IIRC installing gcc-multilib will fix it, although the package name likely varies across Linux distros.