In reply to @matthewcroughan:defenestrate.it

Trying to update a package, but finding this

rcodesign> error[E0282]: type annotations needed for `Box<_>`
rcodesign>   --> /build/rcodesign-0.27.0-vendor.tar.gz/time/src/format_description/parse/mod.rs:83:9
rcodesign>    |
rcodesign> 83 |     let items = format_items
rcodesign>    |         ^^^^^
rcodesign> ...
rcodesign> 86 |     Ok(items.into())
rcodesign>    |              ---- type must be known at this point
rcodesign>    |
rcodesign>    = note: this is an inference error on crate `time` caused by an API change in Rust 1.80.0; update `time` to version `>=0.3.35` by calling `cargo update`

(Cross-posting from nix discord, figured I’d get a response here faster)

One would think that localSystem and crossSystem overlap horribly with the three *Platforms (buildPlatform, hostPlatform, and targetPlatform; see stage.nix or the manual). Actually, those identifiers are purposefully not used here to draw a subtle but important distinction: While the granularity of having 3 platforms is necessary to properly build packages, it is overkill for specifying the user’s intent when making a build plan or package set.

Okay, but what if that „overkill” is what I want and what I need? Can I manually specify all the 3 platforms? Does our cross infra consider that possibility?

In reply to @k900:0upti.me
Are you trying to do some sort of Canadian cross setup?