Hi,
I tried the Firecracker 1.4 branch which depends on new crates that will need to be added to Fedora. Should I wait for the release before adding crates, or can they be packaged early while nothing depends on them? (I don't know when the actual release will happen.) Here are specific crate package changes:
A couple things depend on bindgen-0.65 now (and 0.66.1 is available), although they have workarounds, e.g. ExclusiveArch for pregenerated files. This update isn't necessary yet, but it would be nice to have.
Both bindgen-0.65 and firecracker-1.4 depend on bitflags-2, so that update is required. The new bitflags depends on the unpackaged zerocopy and zerocopy-derive for tests. (They have license file issues that are fixed in Git for the upcoming 0.7.0 version but not in stable releases on crates.io, and zerocopy-derive tests have a dep loop on zerocopy.) Fabio, you own bitflags-1, do you want to own the new API package and its deps, or should I submit their package review requests?
The firecracker-1.4 branch relies on an AWS crypto library for VirtIO RNG support. The main aws-lc-rs crate depends on aws-lc-sys and mirai-annotations which will need to be added. The aws-lc library is a separate C++ project which is bundled into the aws-lc-sys crate.[0] Since nothing else in Fedora is using the aws-lc C++ library, my preference would be to leave it as an implementation detail in the crate and not unbundle it or worry about dynamic linking. Is that acceptable for the package?
Thanks.
David