Andreas Herrmann

The tests include some Nix components and might depend on some of the patches made to Bazel in nixpkgs.

https://github.com/bazelbuild/bazel/commit/3c47b4716e6eca2b8ab06253915ef8d1bdd28038 seems to be relevant to the `LIBTOOL` issue. I've tried out a Nix provided cc toolchain to avoid this issue [here](https://github.com/tweag/clodl/commits/migrate-to-bzlmo/). With that the MacOS build proceeds further, but...

/AzurePipelines run (edit: need to comment as aherrmann-da)

The project doesn't need IPv6, so passing `127.0.0.1` instead of `localhost` is a viable work-around. Forgot to mention: I tried passing hints with `addrFamily = AF_INET` in the above mentioned...

Given that it needs to invoke other repository rules it might even lend itself better to a module extension. You can take a look at [`nix_pkg`](https://github.com/tweag/rules_nixpkgs/blob/master/core/extensions/package.bzl) and [`nix_repo`](https://github.com/tweag/rules_nixpkgs/blob/master/core/extensions/repository.bzl) for reference.

Related to the packages part of https://github.com/tweag/rules_nixpkgs/issues/347

@turmanticant thanks for the kind words and for raising this ticket. I haven't looked into the configuration of ZLS under Bazel, yet. So far I have just used ZLS with...

@vctrmn That's great to hear! Let me know if I can help with any pointers about rules_zig. And thanks for the kind words!

> This is done by collecting all transitive zig modules from a set of targets and assign their name to their `main.zig` file. > [...] > ``` > zls_completion( >...

This issue was created before the ZON package format was introduced. At the time the idea was to perhaps have a rule called `zig_build` that could be invoked on a...