Skip to content

Conversation

jayconrod
Copy link
Contributor

Related #854

@jayconrod
Copy link
Contributor Author

@gyliu513, please verify whether this works on your machine. I don't have a ppc64le machine to test this on.

In your WORKSPACE file, change the repository rule for io_bazel_rules_go to this:

git_repository(
    name = "io_bazel_rules_go",
    remote = "https://github.com/jayconrod/rules_go",
    commit = "949935de2050d8cc9fffa09d866f08a93061253b",
)

Then just build any go_binary or go_test.

@jayconrod
Copy link
Contributor Author

Force submitting. //tests/info is failing on Travis CI on Darwin without explanation. This one has been flaky lately.

@jayconrod jayconrod merged commit cff92a1 into bazel-contrib:master Dec 19, 2017
@jayconrod jayconrod deleted the ppc64le-host branch December 19, 2017 16:24
yushan26 pushed a commit to yushan26/rules_go that referenced this pull request Jun 16, 2025
…zel-contrib#1145)

The interface of `repository_ctx.download` and
`repository_ctx.download_and_extract` supports string lists as well as
strings as the value of the `url` argument. This is the ultimate
destination of the `url` attribute in the `tool_versions` dictionary, so
it makes sense for it to support lists as well.

It is often useful to provide multiple download URLs, e.g. when
vendoring deps through a mirror (to guard against issues like [git
archive checksums
changing](https://github.blog/changelog/2023-01-30-git-archive-checksums-may-change/)
while still keeping the canonical download URL) or in an airgapped
setting (to support internal URLs alongside external URLs). This is also
pretty common around Bazel repository rules that download things, e.g.
[http_archive](https://bazel.build/rules/lib/repo/http#http_archive-urls),
so it can be expected to work with `tool_versions` too.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants