Andreas Herrmann

@lamcw Thank you for raising and debugging this and for the detailed report! > `nixpkgs_package` kept being restarted, possibly due to missing dependencies for the rule itself, or something related...

> although I am not sure if `stat`s are any faster than `chmod`s... Good question, I don't have a Mac handy atm to benchmark. Also something to keep in mind...

> I'm conjecturing that `package-env` files are a solution to keep command line arguments shorter. Correct, that's why they were introduced. They are generated [here](https://github.com/tweag/rules_haskell/blob/e1017b429526e6549ef327e80ce7b3f3af3470a3/haskell/private/packages.bzl#L39-L52). > GHC will store the...

I think [user defined build settings](https://docs.bazel.build/versions/2.1.0/skylark/config.html) could be a good solution to this. We could define a profiling build setting, say `@rules_haskell//haskell:profiling`, that defaults to `False` and can be switched...

The user defined build setting allows to have a separate flag controlling profiling mode for Haskell targets. I.e. it decouples this from `-o dbg`. Having this as a command-line flag...

> The user defined build setting allows to have a separate flag controlling profiling mode for Haskell targets. I.e. it decouples this from -o dbg. I think this is still...

Thanks for raising this! Adding it to the Nix shell would not propagate it into the build actions themselves. For that the dependency needs to be declared in Bazel. @AlexeiDrake...

See https://github.com/tweag/rules_nixpkgs/pull/128#issuecomment-729835453 and https://github.com/tweag/rules_nixpkgs/pull/128#issuecomment-732941362 for why the `-x c++` flag is necessary. > I don't think the explicit definition is needed - since compilers generally can figure that out by...

To copy the extra context from https://github.com/tweag/rules_nixpkgs/pull/185: It seems to be specifically a Nix provided Bazel with a rules_java provided toolchain that fails in this way. A Nix provided Bazel...

Thank you! > Add a version or package parameter to nixpkgs_go_configure to specify explicitly the Go version to track. Other `rules_nixpkgs` rules provide an `attribute_path` attribute for that purpose, e.g....