Eelco Dolstra
Eelco Dolstra
> Nixpkgs has an ever growing number of PR's but not enough people to review and merge them The solution to this is to modularize (split) Nixpkgs. For example, most...
I agree that implicit effects are probably better for our use cases. One downside is that caching of evaluation results between runs becomes harder since you'd have to keep track...
A bit more background on this. There are two problems in Nix: ## Values don't have names This is primarily annoying for error messages / documentation. For example, in ```...
Nickel is supposed to be lightweight and adding a dependency on Jupyter makes it pretty heavy-weight. I'm also a bit skeptical whether there is a lot of overlap between Jupyter...
I'm not really opposed to it being valid, but I don't think it's a good idea to use it in Nixpkgs because it's pretty ugly. Munging the package name (like...
Some considerations: * It's not just aesthetics, it's also confusing. The `"4Blocks"` in `{ "4Blocks" }` looks like a string, not a variable name. * You can't refer to such...
Why not just copy everything to $out/bin?
Hm, what's the use case for this?
Setting ``` nix.extraOptions = "gc-keep-outputs = true"; ``` in your configuration.nix should prevent this.
The user under which builds are executed must be a "trusted" user, i.e. you should add it `trusted-users` in `/etc/nix/nix.conf` (and restart nix-daemon): ``` trusted-users = hydra-queue-runner ```