> > But that is no different from what we have today. Users who update their > > qemu and see issues with libvirt can also be asked to update libvirt. I > > have already had several cases where I needed to do that anyway. > > The general policy of QEMU has been to try and avoid known breakage of > existing apps unless unavoidable. This change introduced 100% guarenteed > breakage of every single deployment that exists today, for the sake of > removing 2 characters from a string. I really don't think this is a good > cost/benefit tradeoff & agree with Cole that I'd like to see this reverted > for the 0.13 release, and re-considered in a later release once we've had > a chance to get a preventative fix out for libvirt using -version-string > or equivalent.
For a stable release I'd agree, we shouldn't be breaking anything. If combined with a version version bump I care a lot less. Paul
