"Release" vfio-ioctls 0.2.0 and upload to crates.io

[cblichmann]

Hey there!

We're depending on vfio-ioctls (among others) via Cloud Hypervisor (CHV). I want to import all of CHV's downstream dependencies into our mono-repo and it'd be super helpful if a more current version were available on crates.io.

So my questions is, what is the current status? Can someone "release" a 0.2.0 and upload to crates.io, or is there some more work planned before this happens?

[liuw]

Hi, while it may be nice to have things on crates.io, I think cargo vendor should work just as well for commit hashes, too. Your request is more a nice-to-have than a must-have, right?

[cblichmann]

I cannot use cargo vendor internally, so it would make my life easier if we had frequent releases to crates.io.
But yes, more of a nice-to-have than a must-have.

[Gasila5]

Hi, while it may be nice to have things on crates.io, I think cargo vendor should work just as well for commit hashes, too. Your request is more a nice-to-have than a must-have, right?

[bytefire]

Hi, is there a good reason not to update crates.io? E.g. are there some features or fixes which need to be done to reach a checkpoint where we can update crates.io?

A side note: Currently the sample code on https://crates.io/crates/vfio-ioctls won't compile because the 0.1 crate expects container device_fd as argument to VfioContainer while the sample code expects it to be Optional (which will work with code in this repo but not with 0.1 crate).