| 24 Nov 2025 |
 dish [Fox/It/She] | which is to say, not good | 14:44:37 |
 @rosssmyth:matrix.org | 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:matrix.org | 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:matrix.org | That's basically yanked packages, which that prototype tool already filters out automatically. But unfortunately yanked packages cannot be relied on. | 17:34:37 |
| @rosssmyth:matrix.org | * 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 |
| @rosssmyth:matrix.org | Since it could be an unmaintained package, so the author would not yanked it | 17:35:13 |
| @rosssmyth:matrix.org | * Since it could be an unmaintained package, so the author would not yank it | 17:35:17 |
