Use crates.io over git for dependencies

[djacu]

Problem

The presence of git dependencies can be problematic for build systems like Nix. progenitor as a git dependencies and progenitor-client as a registry causes the build to fail because it tries to vendor progenitor-client from two places: from crates.io as a direct dependency, and from GitHub as a transitive dependency of progenitor.

I would like to add oxide-rs to nixpkgs. Currently, I have a draft PR in using my fork and some modifications to make packaging possible and so @sarcasticadmin and I can test the CLI application. NixOS/nixpkgs#366077

Solution

• Use the registry for dependencies when possible. It is most important when a diamond dependency can be created as in the case of progenitor.
• Use the patch mechanism of cargo to change the source of dependencies during development. As is currently being done here:

  oxide.rs/Cargo.toml

  Line 91 in ed2163f

  #[patch."https://github.com/oxidecomputer/progenitor"]

  .

Other

A secondary ask but not currently critical to resolving this issue. Please consider publishing oxnet and thouart to crates.io. It would make packaging the software in nixpkgs easier as we would not have to vendor the lock file.

[sarcasticadmin]

Thanks @ahl for the changes in #952

For releases after 0.9.0+20241204.0.0 we should be able to package oxide.rs in nixpkgs without having to do any extra patching.