Alex Eagle
Alex Eagle
I'm on the fence about shipping 2.0 final so long as you can't replace rules_pkg in our js_image_layer example. @thesayyn WDYT?
IIUC, We'll probably want to wait for https://github.com/bazelbuild/bazel/pull/19944 to be available in Bazel 7.0 and direct users to upgrade so that we can handle the cases correctly under bzlmod.
Ooh thanks! @thesayyn could you TAL?
We have a bunch of go programs in this repo already. That's an option if there isn't a simpler solution.
It might be a good idea to file an issue for this first, in case others want to contribute a fix for it.
> Uutils has a statically linked variant of coreutils available as an alternative release artifact. Could bazel-lib use this That sounds great! We'd rather have a larger download and get...
I can't reproduce, I'm trying this in an external workspace in this repo: ``` cd e2e/smoke bazel build @aspect_bazel_lib//lib/tests/yq:all ``` and it succeeds.
Sorry, I don't mean to say there isn't a bug, I just need some help to reproduce it so I can add a test case for it and verify a...
We already had to add `ord` for a base64 implementation in starlark https://github.com/aspect-build/bazel-lib/blob/0fc838839c41677b18245152ad50759233c53794/lib/private/strings.bzl#L521 So I think that path of fixing the mtree we write following the spec is viable
> add that to your build and release workflows If we did go that route - we already have release automation to build four other Go utilities and expose them...