Philip Taron
Philip Taron
@n8henrie @timokau as the relevant folks
> Unstable or a release? I also like unstable. I followed the existing flake for hints as to which version is preferred here, and I'll update it to that branch...
## Use of `package.nix` > For the moment it looks like you're [using this project](https://github.com/philiptaron/flock.nix/blob/4e6bb7d0ce689e6237728c00cc45afa4c89b32ab/nix.nix#L43) in a pretty straightforward way. For sure, and one reason is that I wasn't able...
## Why `package.nix` not `default.nix`? [Because `pkgs/by-name` does it that way](https://github.com/NixOS/rfcs/blob/master/rfcs/0140-simple-package-paths.md), on the grounds that having a package (something that fits into [`callPackage`](https://nix.dev/tutorials/callpackage)) be named `package.nix` is clearer than naming...
The `default.nix` is there as an alternative to flakes. I'm loath to reshape it further.
I am indeed. Let's continue the discussion there.
For future reference: https://nix.dev/tutorials/callpackage is the produced work.
I also was unable to get this to work at all, even with futzing to remove `runMonitoredCommand` when `NIX_GET_COMPLETIONS` was set. (The `Finished at 22:26:31 after 0s` is coming from...
I'm planning on closing this in a week. I don't like unmerged PRs on my dashboard 🔢.
How much of an issue is this performance problem? My opinion is that the discoverability pays for the slower performance, and for production use, when llama.cpp is (for instance) in...