Add [email protected] #430
Conversation
seh
force-pushed
the
impound-rules_cue-module
branch
from
9416731 to
85c9abf
Compare
|
+1 for @seh's fork becoming "official" |
seh
force-pushed
the
impound-rules_cue-module
branch
3 times, most recently
from
4eabd00 to
aea467d
Compare
|
There's some problem with downloading the built cue tool as a release artifact for some of the platforms. I'll investigate that next. |
Head branch was pushed to by a user without write access
seh
force-pushed
the
impound-rules_cue-module
branch
from
aea467d to
93e9aad
Compare
The release artifacts for the cue tool built for Windows are ZIP archives. The code now accommodates that case (again). |
Impound Bazel rules for the CUE language's "cue" tool defined in the "seh/rules_cue" GitHub repository. Withdraw promised support for Windows until we resolve #17487.
Head branch was pushed to by a user without write access
seh
force-pushed
the
impound-rules_cue-module
branch
from
93e9aad to
203f55a
Compare
|
Repeating the comment I added in the presubmit.yml file, some valid invocations of the cue tool can't succeed (e.g. use of the "path" and "expression" rules attributes) until we resolve or find a reliable workaround for bazelbuild/bazel#17487. Until then, withdraw promised support for using this module on Windows. |
Impound Bazel rules for the CUE language's cue tool defined in the seh/rules_cue GitHub repository.
Note that the source repository started as a fork of the tnarg/rules_cue repository, but it hasn't shared any remaining code for a long while. On 10 January 2023 in the "CUE" Slack workspace, I asked @tnarg whether he intends to register his rules_cue repository with the BCR. Today he noted that he's no longer using CUE actively, and offered to advocate for my fork going forward.