-
Notifications
You must be signed in to change notification settings - Fork 9
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
Use vscode-shellcheck/shellcheck-binaries (which gives us Apple Silicon, Windows, And Rasberry Pi support) #30
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, and it is needed in my case too
@aignas is it ok for you? |
Thinking about this a little more, we should support pulling all of the binaries from either the upstream or the vscode github repo. At the end of the day we would be pulling from GH, defaulting to the vscode repo would make sense. What is more, adding all of the available platforms would be also good. |
If you are OK with it, I would gladly update this to pull all binaries (and add all the supported platforms) from the vscode-shellcheck/shellcheck-binaries releases. Does it then make sense to pull from anything but those locations? If so, let me know what you would like and I can help make it so. |
Thanks, that would be great. Whilst you are at it, could you also add the extra supported platforms as well?
…On 3 January 2024 04:22:24 GMT+09:00, Stefan Penner ***@***.***> wrote:
If you are OK with it, I would gladly update this to pull all binaries from vscode-shellcheck/shellcheck-binaries releases.
--
Reply to this email directly or view it on GitHub:
#30 (comment)
You are receiving this because you were mentioned.
Message ID: ***@***.***>
|
1491037
to
11daa6c
Compare
Let me work on that. |
cc15fa0
to
0986ab6
Compare
I've switched this to always use the binaries provided by: https://github.com/vscode-shellcheck/shellcheck-binaries This could be good for another view. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's switch to x86_64 everywhere and this will be good for merging. Maybu adding a bazel skylib build_test to ensure that we can fetch each platform-specific binary would be nice to have, but I am happy to leave this out of the scope of this PR.
395631f
to
224f627
Compare
✅ Complete
That is a good idea, unfortunately I'm a little strapped for time or I would gladly doit. |
Consider doing bazel fetch on the shellcheck target to check that repo definitions are correct for all platforms. |
…check/shellcheck-binaries This adds support for the following architectures: * darwin_aarch64 (apple silicon) * linux_armv6hf (raspberry pi) * windows_x86_64
224f627
to
44c0e49
Compare
Good catch, linux arm -> aarch change has been added, and now |
Merged as the examples are broken due to bzlmod by default, which will need to be fixed separately. Thanks for the contribution! |
@aignas thank you for the reviews! Could I ask when a release might be cut? |
I'll be looking into that next week.
…On 5 January 2024 01:20:28 GMT+09:00, Stefan Penner ***@***.***> wrote:
@aignas thank you for the reviews! Could I ask when a release might be cut?
--
Reply to this email directly or view it on GitHub:
#30 (comment)
You are receiving this because you were mentioned.
Message ID: ***@***.***>
|
Has been released in bazelbuild/bazel-central-registry#1303 |
Thank you for this PR! This was our last dependency to move over to bzlmod due to the arm64 binary being missing |
@aignas thanks for the merge & release! Migrating our internal usage over to mainline now. |
Use vscode-shellcheck/shellcheck-binaries (which gives us Apple Silicon, Windows, And Rasberry Pi support)