| 13 Aug 2024 |
 emily | extra stuff would get propagated into the vendor directory and then just not used | 14:06:56 |
| emily | In reply to @reckenrode:matrix.org
I thought cargo could use foo-0.2 and foo-0.3 if they were needed by transitive dependencies. yes | 14:07:00 |
| emily | 0.2 and 0.3 are major versions though | 14:07:05 |
| emily | ^0.2 and ^0.3 are incompatible, but ^1 and <=1.3 aren't | 14:07:22 |
| emily | so even if 1.5 exists, it will pick 1.2 for both latter requirements because of global version resolution | 14:07:31 |
| emily | (again AIUI, I don't know the exact details) | 14:07:36 |
| emily | so with ^1, <=1.3, ^1.4, ^2 all in the dependency tree, it'd pick 1.3, 1.5, 2.99 | 14:08:11 |
| emily | (and my current idea of what we should do for Nixpkgs would mean we'd have packages dep_1 (1.5), dep_1_3 (packaged because something wants <=1.3), dep_2 (2.99), end up propagating them all into the vendor directory and it'd just work) | 14:10:37 |
| emily | thinking it'd look something like pkgs/rust-crates/dep/{{1,1.3,2}.json,overrides.nix}, where the latter would be hand-written and specify things like non-Rust dependencies, environment variables, perhaps features we want to inject, etc. | 14:11:37 |
| emily | (considered pkgs/by-name but don't think it'd work for this. an end-user would never want to consume one of these anyway; we'll instead have e.g. pkgs/by-name/ri/ripgrep/package.nix doing something like { rustPackages }: rustPackages.toRustApplication rustPackages.crates.ripgrep_latest) | 14:12:20 |
| emily | P.S. send your best cargo shipping software pun names directly to my address | 14:13:26 |
 benjamin | is there a way to select specific targets with fromManifestFile in fenix? | 18:51:17 |
| benjamin | (I'm trying to refactor a package that was previously using fromToolchainFile to avoid IFD) | 18:51:30 |
 linj | hmm, how can I find all packages using rustPlatform, either buildRustPackage or various hooks? I made some changes to those rust hooks and want to check if I break some packages. | 19:04:19 |
| emily | ripgrep is probably your best bet | 19:06:44 |
 a-kenji | In reply to @me:linj.tech
hmm, how can I find all packages using rustPlatform, either buildRustPackage or various hooks? I made some changes to those rust hooks and want to check if I break some packages. If you can build a bit nixpkgs-review should work. | 19:07:26 |
| benjamin | In reply to@benjamin:computer.surgery
is there a way to select specific targets with fromManifestFile in fenix? turns out targets.${target}.fromManifestFile works | 19:08:47 |
| linj | In reply to @a-kenji:matrix.org
If you can build a bit nixpkgs-review should work. hmm, I failed to parse this sentenceš„² is it "if you can build a bit, nixpkgs-review should work"? | 19:08:56 |
| emily | yes | 19:09:25 |
| emily | if you want to rebuild all rust stuff after your change nixpkgs-review is a good option | 19:09:36 |
| emily | I just assumed you were trying to avoid that :) | 19:09:39 |
| a-kenji | Yes. Sorry I am on mobile right now. | 19:09:44 |
| linj | so "build a bit" means have a powerful computer? | 19:10:41 |
| emily | or a lot of patience | 19:10:49 |
| linj | * so "build a bit" means having a powerful computer? | 19:10:50 |
| emily | if you don't have a ton of CPU cycles to spare, you might want to apply for access to some of the community build boxes | 19:10:59 |
| linj | oh, good idea | 19:11:23 |
| emily | https://nix-community.org/community-builder/ https://github.com/NixOS/aarch64-build-box | 19:11:26 |
| linj | I already have access to the darwin box | 19:11:35 |
| emily | we have x86_64-linux, aarch64-linux, aarch64-darwin | 19:11:35 |
