| 8 Aug 2025 |
 aidalgol | None of the guides for normal cross-compilation in nixpkgs quite fit this odd scenario. | 22:10:54 |
| aidalgol | i.e. https://wiki.nixos.org/wiki/Cross_Compiling and https://nix.dev/tutorials/cross-compilation.html by my reading are describing setting up a dev environment for cross compiling using nixpkgs, not packaging, say, a Windows executable for use in an x86_64-linux NixOS package. | 22:15:33 |
| aidalgol | Comet's upstream releases include GalaxyCommunication-dummy.exe, but our comet-gog package does not. I think this .exe was added upstream sometime since the nixpkgs package was added. | 22:18:14 |
| aidalgol | * Comet's upstream releases include GalaxyCommunication-dummy.exe, but our comet-gog package does not because it only builds comet. I think this .exe was added upstream sometime since the nixpkgs package was added. | 22:18:27 |
| 9 Aug 2025 |
| aidalgol | SigmaSquadron: Is there anything we can do around the heroic package to get people to bother nixpkgs people first rather than going straight to upstream? This happens a lot. | 02:06:48 |
 SigmaSquadron | Could patch the sources so whenever we get an error message, it provides a link to Nixpkgs instead. | 02:22:45 |
| aidalgol | Yeah, maybe I should do that. I've been hesitant to modify the upstream source much. | 02:57:14 |
| aidalgol | Regarding the Windows helper executables, I have packaged them in PR#432183, and I'm not sure the way I have done so is acceptable in nixpkgs, so I would really appreciate a review on this. | 05:42:20 |
