On Mon, Oct 31, 2016 at 02:59:59PM +0300, Ponomarenko Andrey wrote: > Hello, > > The API/ABI interface of the libguestfs library is now checked for backward > compatibility in the Upstream Tracker project: > https://abi-laboratory.pro/tracker/timeline/libguestfs/ > > Hope the report will be helpful for users and maintainers of the library.
A few things: You can ignore guestfs_internal_* APIs. As the name suggests no ABI guarantees are made for those symbols. I don't agree with the conclusions in this web page related to guestfs_add_domain_argv and guestfs_add_drive_opts_argv: https://abi-laboratory.pro/tracker/compat_report/libguestfs/1.26.10/1.28.12/4fad9/abi_compat_report.html The initial bitmask in the struct controls which fields are present, and we handle old caller / new library (and indeed new caller / old library) correctly as far as I know. I understand that there's insufficient information in a C header file to really describe this stuff, but there we are. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://people.redhat.com/~rjones/virt-top _______________________________________________ Libguestfs mailing list [email protected] https://www.redhat.com/mailman/listinfo/libguestfs
