Fabian Meumertzheim
Fabian Meumertzheim
@aranguyen https://docs.google.com/document/d/1L1JFgjpZ7SrBinb24DC_5nTIELeYDacikcme-YcA7xs/edit?usp=drivesdk
> Would it make sense to create entries in the Bazel registry with my repos and eventually switch it to the official ones when my patches are accepted? I agree...
We just migrated some internal usages of the `@bazel_tools` version of `rules_pkg` and noticed that the behavior of `include_runfiles` was subject to a breaking change with https://github.com/bazelbuild/rules_pkg/commit/7a991dea418ab17c7e86f0a7b5e7d4a87ef4304b. In its current...
The WORKSPACE tests are failing since they use a different repo name for Stardoc, which now appears in `load` statements. How do you want me to deal with that?
I'll wait for #232 then, let me know what I need to do after it has been merged.
@rickeylev Would it be possible to extract this setup into a `rules_sphinx`? I'm pretty sure that other rulesets would love to adopt it.
> Regarding extracting into `rules_sphinx`: since Sphinx is in Python, you probably need `rules_python` to use it anyway, so breaking this out won't spare anyone any dependencies, will it? Breaking...
rules_java 6.5.0 requires Bazel 6.4.0 (not yet released) or a recent rolling release.
@spaghettifunk Are you loading rules_java at the very top of your WORKSPACE? It's possible that some other dep pulls in an older version.
Since GraalVM can't cross-compile native images, at least for full parity this would require having real Linux AArch64 machines in Bazel CI. cc @meteorcloudy