| 29 Mar 2026 |
 Randy Eckenrode | It’s to create wrapper app bundles for applications that just have a binary and an icon. That’s a distinct use case from generating wrappers for .desktop files. | 14:08:25 |
 eveeifyeve | Can't you just do that with the install command? | 14:09:02 |
| Randy Eckenrode | No. This is for applications that ship only a bare $out/bin/<exe>. Not everything that builds and runs on Darwin bothers to create a nice app bundle for it. | 14:10:35 |
| eveeifyeve | So is this useful relating to nix bundlers? | 14:12:30 |
| Randy Eckenrode | There’s probably an argument that all the ways to make app bundles should use a common set of primitives. I don’t think they do right now. | 14:12:32 |
| Randy Eckenrode | What do bundlers do? | 14:12:57 |
| eveeifyeve | bundler is a function over a value (useally a drv) that produces another drv. | 14:14:10 |
| eveeifyeve | So like hello, produces a docker image. | 14:14:24 |
| eveeifyeve | * So like hello, produces a docker image with hello. | 14:14:34 |
| eveeifyeve | Which is based on the nix bundle command, which it's intended usecase is to make anything work outside of the store. | 14:15:14 |
| eveeifyeve | * Which is based on the nix bundle command, which it's intended usecase is to make anything work outside of the store/without nix. | 14:15:24 |
| Randy Eckenrode | What is the user-facing output of, e.g., makeBinaryBundle? | 14:15:26 |
| Randy Eckenrode | Ah, there it is. What’s the expected level of support? | 14:16:07 |
| eveeifyeve | I am not too sure, I would assume none. | 14:16:46 |
| eveeifyeve | * I am not too sure, I would assume none outside of the store/without nix. | 14:17:04 |
| Randy Eckenrode | Why does this need to be upstreamed (vs. remaining in a third party repo that can iterate more quickly and not be tied to nixpkgs releases)? | 14:17:16 |
| Randy Eckenrode | Though it sounds like this is targeting more than Darwin with the deb stuff. | 14:18:26 |
| eveeifyeve | Overall I think it's a great idea to have it in nixpkgs for accessability, documented on how to use it and comes with greater community adoption. | 14:19:25 |
| eveeifyeve | Like it makes it at a fingertip that packages from nixpkgs can just be used for another package repo. | 14:20:13 |
| eveeifyeve | * Like it makes it at a fingertip that packages from nixpkgs can just be used for another package repo. Helps businesses use nix as a CI tool (which is what it's made for) | 14:20:48 |
| eveeifyeve | * Like it makes it at a fingertip that packages from nixpkgs can just be used for another package repo. Helps businesses use nix as a CI tool (which is what tomberek proposed) | 14:22:09 |
| eveeifyeve | Write the package once, use everywhere. | 14:22:48 |
 K900 | Except bundlers have like 300000 different caveats especially on Linux | 14:24:36 |
| eveeifyeve | * Like it makes it at a fingertip that packages from nixpkgs can just be used for another package repo. Helps businesses use nix as a CI tool (which is what nix is made for) | 14:24:39 |
| K900 | That have consistently remained unaddressed and will probably stay that way unless you want to, like, port most of pressure-vessel | 14:25:12 |
| K900 | (and even that comes with other bonus caveats) | 14:25:25 |
| eveeifyeve | Like what? | 14:25:58 |
| K900 | Like graphics drivers | 14:26:05 |
| eveeifyeve | * Like what? Give me some examples. | 14:26:11 |
| eveeifyeve | Nix-user-chroot. | 14:26:40 |
