Re: [Libguestfs] Versioning of rust bindings
On Tue, Aug 06, 2019 at 06:04:22PM +0900, Hiroyuki Katsura wrote:
In the last patch, I let the version of Rust bindings be the same as
the
version of libguestfs. However, I came to think it is not preferable in
terms of the custom of Rust crate versioning.
After a version of a crate is published to crates.io, no one can republish
the crate with the same version. This means that when there are some
mistakes in the rust bindings, after they are fixed, it is required to add
the version to publish it. I'm not sure about the versioning of libguestfs,
but I believe that it is not preferable that the versioning issue of rust
bindings affects the whole versioning of libguestfs.
Though it is available to hack SemanticVersioning by using suffixes(as we
discussed before), maybe it is not preferable like 1.40.0-ver1.
So, I think the versioning of rust bindings should be independent of the
one of libguestfs.
Do you agree, or not?
It's up to you, but it seems like there ought to be some connection to
the stable version. For example that a particular version of the
bindings is compatible with / works best with libguestfs 1.40.
That doesn't mean that the Rust bindings need to have the
exact same version (like "1.40.99"). You can even put the
stable version something else in the version string, like
guestfs-sys 2.5-compat1.40 or something.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-p2v converts physical machines to virtual machines. Boot with a
live CD or over the network (PXE) and turn machines into KVM guests.
http://libguestfs.org/virt-v2v