Nix Rust | 661 Members | |
| Rust | 154 Servers |
| Sender | Message | Time |
|---|---|---|
| 24 Nov 2025 | ||
In reply to @niklaskorz:matrix.orgat the end of the readme, says about 50MB x_x | 14:32:42 | |
| well maybe we shouldn't include the whole cargo-verse | 14:43:56 | |
| if we try to do filtering we end up like nodePackages | 14:44:26 | |
| which is to say, not good | 14:44:37 | |
| 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 | |
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 | |
| That's basically yanked packages, which that prototype tool already filters out automatically. But unfortunately yanked packages cannot be relied on. | 17:34:37 | |
| * That's basically yanked packages, which that prototype tool already filters out automatically. But unfortunately yanked packages cannot be relied on for security. | 17:34:48 | |
| Since it could be an unmaintained package, so the author would not yanked it | 17:35:13 | |
| * Since it could be an unmaintained package, so the author would not yank it | 17:35:17 | |
| I have another PR up that if combined with yanked package elimiation would catch CVEs https://github.com/NixOS/nixpkgs/pull/458881 | 17:36:16 | |
| * I have another PR up that would catch CVEs https://github.com/NixOS/nixpkgs/pull/458881 | 17:36:25 | |
| oh that's amazing! | 18:16:46 | |
| 25 Nov 2025 | ||
| Why not do it like this and collect them using nix?
| 14:10:21 | |
| just realized I'm running Hacksaw with xcb-0.9, which contains a CVE 💀 i hope bumping it to 1.6 won't break anything | 14:13:02 | |
| Yes of course there is more processing to do. This was just an idea I had and I wanted to see how large the JSON file would actually be. This doesn't actually change anything. | 19:05:27 | |
| * Yes of course there is more processing to do. This was just an idea I had and I wanted to see how large the JSON file would actually be. This doesn't actually fix anything. | 19:12:04 | |
| This should help with merge conflicts I think, no? | 19:56:20 | |
| The idea of processing all the crates into one file is to eliminate merge conflicts from being possible in the first place | 19:58:38 | |
| Since the maintainer(s) of the package set would just regenerate the entire file every week or so | 19:59:03 | |
| Another idea I have been ruminating upon is something like:
| 20:09:31 | |
| Yeah that's basically what I wanted to achieve with my script | 21:07:07 | |
| 28 Nov 2025 | ||
| 18:06:53 | ||
| 29 Nov 2025 | ||
| 11:40:45 | ||
| 30 Nov 2025 | ||
| 22:49:08 | ||
| 1 Dec 2025 | ||
| Hello. I've been using nix and nixos for a while. I noticed that in the changelog for the new stable release that there was a few rust projects. How can I get involved as a newcomer, with some decent rust and nix experience? | 01:16:38 | |
In reply to @akompella:matrix.orgeveryone can submit their fixes to Nixpkgs. if you wanna take responsibility for specific packages/modules, add yourself to their maintainers (see readmes under maintainers and pkgs on how) | 04:47:35 | |
| Thank you. I am planning currently to submit a PR to nixpkgs for a package I haven't seen on there, and I'll take a look at taking responsibility for other packages once I go through the process once myself, I hadn't considered that. However, I was asking more about the nix / nixos tooling / projects rather than projects in nixpkgs. | 08:34:44 | |
| Nixos tooling that is Rust mostly lives inside nixpkgs | 09:03:53 | |
| Nix itself doesn't use Rust | 09:03:58 | |