Andreas Herrmann

> > Could dep_direct_mods and potentially dep_direct_pks be used to identify unused direct module dependencies? > > How would you determine then which interface files are unused? I was thinking...

Yes, as I understand this could only be used to determine unused direct module dependencies.

@regnat's suggestion sounds like a good workaround and it seems to be working with `ghci` from `haskell_repl`. For example the following command generates hie files for one of the test...

@ryanrasti Thanks for raising this, it's an interesting question! A common way to create Docker images with Nix+Bazel is to use Nix to generate a base image, and then use...

> A very common case for me is that I want to rely on some binary being in PATH so that when I depend on a nix target in bazel...

An alternative approach that could be utilized in something like `buildBazelPackage` is to make the required Nix packages a dependency on the Nix level and pass them in using [`--override_repository`](https://docs.bazel.build/versions/main/external.html#overriding-repositories-from-the-command-line).

@layus > it is hard to specify the ENV_NIX_REMOTE_KEY_FILE when it is located in the repository. You need to expand %workspace% and bazel will not do that for environment variables,...

I consider the question of env-var or not an implementation detail. What I consider important is the following: 1. I'd like to be able to switch off remote builds temporarily,...

This issue is avoided when the nixpkgs repository is declared using `nixpkgs_local_repository` instead of referring to the file `//:nixpkgs.nix` directly. `nixpkgs_local_repository` correctly fails when `inc.nix` is not declared. See https://github.com/tweag/rules_nixpkgs/commit/93e706d7c5120adf336dc7e2aec3e73b74a53fb2....

> Do repository rules now support providers? Sadly they don't. Furthermore, one cannot directly depend on a repository rule. `@nixpkgs` is just a shorthand for `@nixpkgs//:nixpkgs`.