> If cargo as a tool behaved more like pip, where you'd call `cargo install dependency` and then completely unconnected `rustc build` This has the problem that

> If cargo as a tool behaved more like pip, where you'd call `cargo install dependency` and then completely unconnected `rustc build` This has the problem that your deps can get out of sync with your lockfile... which is why most/all the newer python package managers have a run command that works more like cargo e.g. https://python-poetry.org/docs/basic-usage/#using-poetry-run https://python-poetry.org/docs/basic-usage/#using-poetry-run If you tried it a while ago things likely improved since then. `cargo fetch` and `cargo vendor` are both single-command solutions for airgapped networks.