| 20 Nov 2025 |
rosssmyth | * Not that I am aware of. You may be able to hack something together with fastCross. But the way the rustc derivation is setup right now makes it hard to just compile a sysroot for a target without structuring all of your Nixpkgs instance around it. | 21:38:35 |
rosssmyth | You may be able to do something funny like setting the platforms to a wasi and require people to use pkgsCross.wasi32. But I have no idea what the state of compiling for wasi32 is or if that would work. Would be annoying for end-users though. | 21:41:41 |
Sandro 🐧 | mitmproxy-linux is cross compiling without anything extra to something wasm | 21:46:52 |
Sandro 🐧 | *ebpf not wasm | 21:49:53 |
Sandro 🐧 | your target is missing here https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/compilers/rust/rustc.nix#L158-L161 though | 21:50:09 |
Sandro 🐧 | maybe this hint https://github.com/NixOS/nixpkgs/blob/master/lib/systems/default.nix#L504 helps | 21:51:07 |
dotlambda | I would hope that adding something like pkgsCross.wasi32.buildPackages.rustc does the trick | 22:03:08 |
rosssmyth | Probably will, but that has the downside of instantiating a whole other nixpkgs | 22:03:38 |
dotlambda | pkgsCross.wasi32 is also used to build Firefox | 22:04:06 |
dotlambda | In reply to @robert:funklause.de I would hope that adding something like pkgsCross.wasi32.buildPackages.rustc does the trick Sadly, it fails to build with a complaint about missing a "wasi-root" key in bootstrap.toml | 22:09:51 |
| 21 Nov 2025 |
| Diogo Correia joined the room. | 09:01:19 |
Diogo Correia | Some progress on this over at https://github.com/NixOS/nixpkgs/pull/463720 | 11:21:35 |
| amadaluzia changed their display name from amadaluzia to amadaluzia (🇹🇷 til 25th). | 14:45:43 |
| isabel changed their profile picture. | 18:14:28 |
| @some1deleted:matrix.org left the room. | 21:23:24 |
| 22 Nov 2025 |
| raizo joined the room. | 12:27:32 |
| @cuer:envs.net removed their profile picture. | 15:09:23 |
| @cuer:envs.net removed their display name Cuer. | 15:09:26 |
| @cuer:envs.net left the room. | 15:09:28 |
| 24 Nov 2025 |
rosssmyth | Some experimenting I was doing today
https://github.com/RossSmyth/fetch-cargo-index | 01:02:15 |
niklaskorz | so how big is the generated index? 😅 | 10:50:28 |
Acid Bong | it'd be more convenient if Crates themselves forbade downloading insecure libraries | 11:08:36 |
| amadaluzia changed their display name from amadaluzia (🇹🇷 til 25th) to amadaluzia. | 12:57:05 |
dish [Fox/It/She] | In reply to @niklaskorz:matrix.org so how big is the generated index? 😅 at the end of the readme, says about 50MB x_x | 14:32:42 |
niklaskorz | well maybe we shouldn't include the whole cargo-verse | 14:43:56 |
dish [Fox/It/She] | if we try to do filtering we end up like nodePackages | 14:44:26 |
dish [Fox/It/She] | which is to say, not good | 14:44:37 |
rosssmyth | Yeah unfortunately I'm unsure of a much better way.
Only including deps that Nixpkgs requireds in a json file quickly would become similar to nodePackages, where every time a crate is added it is required to modify a file which results in merge conflict hell usually, especially if it is minimized to reduce storage space requirements | 17:33:00 |
rosssmyth | The other idea would be to have a package set that is similar to all-packages, which I think tooling could be made that wouldn't make it too bad | 17:33:35 |
rosssmyth | That's basically yanked packages, which that prototype tool already filters out automatically. But unfortunately yanked packages cannot be relied on. | 17:34:37 |