You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
The text was updated successfully, but these errors were encountered:
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`.
This commit changes the Cargo.toml and lock file to pull `progenitor`
from the registry instead of GitHub.
Fixesoxidecomputer#950
Problem
The presence of git dependencies can be problematic for build systems like Nix.
progenitor
as a git dependencies andprogenitor-client
as a registry causes the build to fail because it tries to vendorprogenitor-client
from two places: from crates.io as a direct dependency, and from GitHub as a transitive dependency ofprogenitor
.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#366077Solution
progenitor
.oxide.rs/Cargo.toml
Line 91 in ed2163f
Other
A secondary ask but not currently critical to resolving this issue. Please consider publishing
oxnet
andthouart
to crates.io. It would make packaging the software in nixpkgs easier as we would not have to vendor the lock file.The text was updated successfully, but these errors were encountered: