| 12 Sep 2023 |
 👉@crystallinefire:chat.solarpunk.moe | In reply to @ultra:beeper.com
I was joking XD i'm not i think it would be awesome | 18:38:01 |
 Alex S | In reply to @hive:the-apothecary.club
i'm not i think it would be awesome yeah it would be | 18:38:12 |
 John Ericson | rhelmot: hi | 18:56:02 |
| John Ericson | I feel like we might have talked about this before? | 18:56:09 |
| John Ericson | or maybe just similar conversations with others? | 18:56:15 |
| John Ericson | Have you talked to Alyssa Ross about this? | 18:56:22 |
 rhelmot | No, I don't recall having talked to you or alyssa about this at all. Alyssa has been around while I've been complaining about the in-progress stuff but there's been no intersection. | 18:57:54 |
| rhelmot | John Ericson: can I ask what you mean by not seeing any overlap? My understanding is that the userland is already part of nixpkgs, so a tarball of that could easily replace the impure bootstrap I did. | 19:09:00 |
| John Ericson | the packages you modified we can already cross compile | 19:09:37 |
| John Ericson | and the stuff in pkgs/os-specific/bsd/freebsd should replace most/all of pkgs/stdenv/freebsd | 19:09:57 |
| rhelmot | how does cross compiling help with the case that I'm trying to address, which is that I'm running nix on freebsd? | 19:11:41 |
| rhelmot | correct me if I'm wrong, but in order to use a binary substitute, you need to boot the same stdenv as the builder in order to get the hashes to match? | 19:12:23 |
| John Ericson | I mean there is no reason to modify those packages | 19:12:58 |
| John Ericson | if we can build them cross + pure, we can also build them native + pure | 19:13:19 |
| John Ericson | if you need to change a package, that is not because native, that is because impurities | 19:13:35 |
| John Ericson | the impure stdenv will be a different in a number of small inconsequential but papercut-causing ways | 19:13:54 |
| John Ericson | it is not maintainable to support those paper cuts on every package | 19:14:06 |
| rhelmot | so what's the deal with the various platform checks scattered throughout every package that I've looked at? | 19:14:44 |
| rhelmot | I recognize that I'm new to nix, but I have a hard time believing that the purity guarantees are really that strong, especially on freebsd where you don't get bind mounting. | 19:16:26 |
| rhelmot | like no ill will if all of my work is obsoleted, but I just don't understand it | 19:17:35 |
| John Ericson | there are certainly still platform checks needed | 19:41:23 |
| John Ericson | don't get me worng | 19:41:27 |
| John Ericson | but I just don't think native should need more than cross | 19:41:39 |
| 13 Sep 2023 |
|  mib 🥐 joined the room. | 08:28:08 |
|  @theesm:lispy.eu joined the room. | 22:51:27 |
| 16 Sep 2023 |
|  Majiir Paktu joined the room. | 00:04:14 |
 p14 | I've got a pipeline of things I want to fix to make pkgsLLVM.pkgsStatic to work well, but review is going slow. I don't want to generate a mass of PRs which go unreviewed for a long time since that risks increasing the infinite TODO list for everybody. Any kind souls able to help me clear this review from the pipeline? I hope it is uncontroversial. https://github.com/NixOS/nixpkgs/pull/253116 | 09:06:10 |
| p14 | Alyssa Ross: thanks for the review. (AFK so responding here rather than gh for a moment) Is it possible you have missed that link type is a single word value “static” or “dynamic” according to the output of the checkLinkType function? If not, I don’t understand, can you clarify? | 09:29:09 |
 Alyssa Ross | I did miss that :) | 09:29:26 |
| 20 Sep 2023 |
| rhelmot | I've added to my PR the ability to parameterize the freebsd packages so they can be cross compiled for either freebsd13 or freebsd14. I can now compile all the inputs necessary for the freebsd stdenv. what's the protocol on being able to access a cross-compiled package from a native-booting stdenv? I assume there's some magic somewhere to make it so the hashes line up, but I'm not sure what that would look like. | 07:03:37 |
