From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jamie Lokier Subject: Re: [libvirt] Re: [Qemu-devel] Changing the QEMU svn VERSION string Date: Tue, 7 Apr 2009 18:13:24 +0100 Message-ID: <20090407171324.GB31824@shareable.org> References: <49DABC83.7010608@codemonkey.ws> <49DB0A6C.9080200@redhat.com> <20090407090322.GC31447@redhat.com> <49DB5AAE.8050205@codemonkey.ws> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: veillard@redhat.com, libvir-list@redhat.com, Gerd Hoffmann , kvm-devel To: qemu-devel@nongnu.org Return-path: Received: from mail2.shareable.org ([80.68.89.115]:46719 "EHLO mail2.shareable.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753298AbZDGRN2 (ORCPT ); Tue, 7 Apr 2009 13:13:28 -0400 Content-Disposition: inline In-Reply-To: <49DB5AAE.8050205@codemonkey.ws> Sender: kvm-owner@vger.kernel.org List-ID: Anthony Liguori wrote: > I still think libvirt should work with versions of QEMU/KVM built from > svn/git though. I think the only way to do that is for libvirt to relax > their version checks to accommodate suffixes in the form > major.minor.stable-foo. Ok, but try to stick to a well-defined rule about what suffix means "later" or "earlier". In package managers, "1.2.3-rc1" is typically seen as a later version than "1.2.3" purely due to syntax. If you're consistently meaning "0.11.0-rc1" is earlier than "0.11.0" (final), that might need to be encoded in libvirt and other wrappers, if they have any fine-grained version sensistivity such as command line changes or bug workarounds. The Linux kernel was guilty of mixing up later and earlier version suffixes like this. With Linux this is a bit more important because it changes a lot between versions, so some apps do need fine-grained version checks to workaround bugs or avoid buggy features. Maybe that won't even happen with QEMU and libvirt working together. -- Jamie