Rust bindings lack flexibility with current structure of build script about c-kzg-4844 HOT 3 CLOSED

If we are open to modifying the repo to get cargo vendor to succeed then I'm happy to make a PR to diagnose further.

Hey @ralexstokes! This is an interesting problem. I'm open to changing things. But I would like to hear about this from other Rust people before suggesting we do anything. @pawanjay176 @asn-d6, thoughts?

from c-kzg-4844.

Hmm, it feels dirty to dump Cargo.toml and build.rs to the project root, but it seems like we already have golang and nim-related files there. So dirtiness is already there, and hence I wouldn't oppose this change.

I wonder if it's possible to do something using cargo workspaces. From reading a bit about it, even if it's possible, we would still need a Cargo.toml in the project root to specify the location of the rust bindings.

The extreme (not proposed) alternative is to move all bindings to their own git repo so that they can freely manage their directories.

from c-kzg-4844.

+1 to this issue. I'm using nixos for my DevOps too and it fails to work:(
This is because of strict rules for what application can access, and it fails to vendor the crate.

from c-kzg-4844.