Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mark go_sdk module extension as {os,arch}_dependent #3703

Merged
merged 2 commits into from
Sep 20, 2023
Merged

Mark go_sdk module extension as {os,arch}_dependent #3703

merged 2 commits into from
Sep 20, 2023

Conversation

fmeum
Copy link
Member

@fmeum fmeum commented Sep 19, 2023

What type of PR is this?

Bug fix

What does this PR do? Why is it needed?

This ensures that the lockfile maintains separate instances of this extension for each OS/arch combination.

This ensures that the lockfile maintains separate instances of this
extension for each OS/arch combination.
@fmeum fmeum requested a review from linzhp September 19, 2023 11:15
@fmeum
Copy link
Member Author

fmeum commented Sep 19, 2023

CC @tyler-french

go/private/extensions.bzl Outdated Show resolved Hide resolved
go/private/extensions.bzl Outdated Show resolved Hide resolved
@fmeum fmeum requested a review from linzhp September 20, 2023 14:48
@fmeum fmeum merged commit 7309aba into master Sep 20, 2023
@fmeum fmeum deleted the os-arch branch September 20, 2023 18:43
@tpasternak
Copy link

Hi folks, maybe I should ask the question in bazelbuild/bazel, but do you know if there's any way to cross-build a lockfile for all available architectures after this change? When I do it normally I only get an entry for my own os/arch, which makes it quite difficult to update, as I would have to rebuild lockfile on each of them sequentially...

@fmeum
Copy link
Member Author

fmeum commented Dec 20, 2023

@tpasternak There isn't and given that a module extension can run essentially arbitrary binaries, this can't be done. I'm looking into ways to resolve the situation for go_sdk and similar extensions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants