Revert "stdenv: log build hooks as they run"

[ghost]

Reverts #290081

• the hooks are writing to stdout which will break pipelines that use nix-shell as the interpreter
• default logging is very verbose when using nix-shell

reverting for now -- hopefully this change finds its way back soon

@Qyriad @philiptaron @RaitoBezarius

[lf-]

Please consider instead: nix-shell --no-build-output.

[ghost]

Please consider instead: nix-shell --no-build-output.

https://nixos.org/manual/nix/stable/command-ref/nix-shell.html#use-as-a--interpreter suggests

#! /usr/bin/env nix-shell
#! nix-shell -i real-interpreter --packages packages

so --no-build-output doesn't seem like a viable workaround, unfortunately.

[lf-]

Ah, yeah sorry I realized later I misunderstood the issue. Regressing nix-shell -p is definitely a bit of an ouchie.

There's sneaky stuff that can be done to the logs that can help though, we'll see how that shakes out in the next iteration.

[philiptaron]

Yeah, I'm sad this is getting reverted, though I understand the reason why. @Qyriad, if you want to, we can work together to make the next version. 💪🏻

[ghost]

agree. this is a good change and should make its way back in. looking at it yesterday, perhaps just logging to stderr when NIX_DEBUG is > 0 is sufficient.

[lf-]

agree. this is a good change and should make its way back in. looking at it yesterday, perhaps just logging to stderr when NIX_DEBUG is > 0 is sufficient.

we actually noticed there's extra message types we can send to NIX_LOG_FD, which will ostensibly appear on higher verbosity levels of nix itself, get saved properly, as well as not invalidate derivations when changed. we've not tried it yet but we did find the nix-side code for such a thing. this would probably be the ideal situation, to decouple print verbosity from build configuration.

[Qyriad]

I started to experiment with it briefly today and it seems to be a viable route so far.