Nix Hackers | 932 Members | |
| For people hacking on the Nix package manager itself | 195 Servers |
| Sender | Message | Time |
|---|---|---|
| 6 Mar 2026 | ||
| Hey yall, via nix I installed "jasp-desktop", and it installed the binary "JASP" (in all caps), I'm pretty sure that most binaries are not capitialized, so is this a problem I could make a PR for, or is this normal for nix? (It is just a bit confusing that I cant just run the program with "jasp"). | 18:23:47 | |
| That's mostly up to upstream | 18:38:24 | |
| 19:57:47 | ||
| 7 Mar 2026 | ||
| Did I hear someone say freebsd sandbox building? | 16:22:04 | |
| 8 Mar 2026 | ||
| 23:28:36 | ||
| 9 Mar 2026 | ||
| 22:05:42 | ||
| 10 Mar 2026 | ||
| Sharing this from Spack (spack.io) how they handle OpenGL or runtime type library dependencies:
| 00:18:29 | |
| tl;dr; Spack puts a 128 length padded entry in RPATH for the library (i.e. OpenGL). At realisation, the ELF binary is modified to point to the live running library. | 00:19:15 | |
| not reaaaly an option for nix | 02:24:10 | |
| and for regular rpath rewriting while building, we've been patchelf-ing everything which handles making a new PT_DYNAMIC | 02:25:21 | |
| so that's also not a problem | 02:25:25 | |
| * so that's also "not" a problem | 02:25:35 | |
| Speaking about patchelf, there has been discussion about using fixpath instead. | 07:25:44 | |
| * Speaking about patchelf, there has been discussion about using fixpath or some alternative instead, which I don't remember. | 07:26:18 | |
| * Speaking about patchelf, there has been discussion about using fixpath or some alternative instead, which I don't remember. But the reason is for windows and unix are very different binary formats eg. windows being Pe (portable exe), linux being elf, macos being mach-o. | 07:29:18 | |
| if you mean https://github.com/nixcloud/fixPath i think that's PE-only, so "additionally", not "instead" | 07:33:45 | |
| 08:45:47 | ||
| 12:07:25 | ||
| 14:24:52 | ||
| 14:38:36 | ||
| 11 Mar 2026 | ||
| 03:48:02 | ||
Did something change in the behavior of indirect flakeref resolution? nix registry resolve nixpkgs/a3a3dda3bacf61e8a39258a0ed9c924eeca8e293 works but nix registry resolve nixpkgs/nixos-unstable/a3a3dda3bacf61e8a39258a0ed9c924eeca8e293 fails with error: cannot apply both a commit hash (a3a3dda3bacf61e8a39258a0ed9c924eeca8e293) and a branch/tag name ('nixos-unstable') to input 'github:NixOS/nixpkgs/nixpkgs-unstable' | 09:30:45 | |
| 14:11:47 | ||
| 19:49:40 | ||
| I'm trying to think of a way to asynchronously drain a file descriptor into a sink, is it safe to write to a sink from a different thread, assuming that's the only writer? | 21:51:32 | |
| I think source.drainInto(sink) is good for this, there are different overloads. A buffered sink only cares about having one writer | 22:10:32 | |
| (Same for the source too) | 22:10:55 | |
| alright, I'll give it a shot <3 | 22:13:57 | |
man I don't even have nix registry resolve, is it new? | 22:17:41 | |
| Gonna try something like this:
| 23:03:32 | |