-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nix 0.24 made VsockAddr opaque #24
Comments
Why you guys need such a new version of nix. just curious. Knowing usecases of our users will make the project better. |
In Android we vendor in all third-party dependencies, including Rust crates, and build with Soong (not cargo). This means that we can only have one version of each crate in the tree. We will need to update nix at some point for other users, and so we need the vsock crate to build with the latest version. And even in the cargo ecosystem, it's generally desirable to avoid having multiple versions of the same crate where possible, to reduce build time and binary size. |
I'm in a similar situation as qwandor. Debian packages crates, primarily to serve building bin crates. It's possible for us to have multiple, versioned crates for a single project in Debian, but we try to avoid it if at all possible. We recently bumped nix to 0.24 without realizing that a couple of the dependent packages, vsock included, would be affected by the breaking changes in 0.24. |
nix-rust/nix#1614
vsock won't build with nix >= 0.24.
Build log
The text was updated successfully, but these errors were encountered: