Andreas Herrmann

@midnightconman Thanks for the swift reply and sharing more context about your use-case. > we would prefer the main "entry" binary to be bazel You mean the "entry" binary for...

@AttilaTheFun Thanks for reaching out. > In my ideal world, I would add rules_nixpkgs from my WORKSPACE and use it to configure my toolchains + install nix packages. In BUILD...

@AttilaTheFun That's understandable. As mentioned above there are some limitations to what's possible with Bazel and Nix at the moment. > rules_nixpkgs would be a repository rule Just to clarify...

This could be a good place to use integration tests via https://github.com/bazel-contrib/rules_bazel_integration_test as described in [this blog post](https://www.tweag.io/blog/2022-10-06-bazel-rules-to-test-bazel-rules/).

Thank you for raising this issue! I haven't gone through all the details, yet, but a Go related `mktemp` failure also occurred here: https://github.com/tweag/rules_nixpkgs/pull/423#issuecomment-1743356411 . I've worked around it in...

@contagnas Thanks for raising this. Yes, this sounds like it would be a good addition. > { code: 2, kind: NotFound, message: \"No such file or directory\" } This sounds...

@layus Yes, that's true - and annoying. Unfortunately, I'm not sure what a better approach may look like. Short of defining toolchains.

> I guess I don't really understand how these special paths are arising? They should arise when you enable bzlmod either by `bazel test --config=bzlmod` in `testing/core`, or with `export...

@avdv is this one done now or is there still work remaining here?

@avdv Thanks for clarifying, sounds good!