From: Jamie Lokier <jamie@shareable.org>
To: qemu-devel@nongnu.org
Cc: veillard@redhat.com, libvir-list@redhat.com,
Gerd Hoffmann <kraxel@redhat.com>,
kvm-devel <kvm@vger.kernel.org>
Subject: Re: [libvirt] Re: [Qemu-devel] Changing the QEMU svn VERSION string
Date: Tue, 7 Apr 2009 18:13:24 +0100 [thread overview]
Message-ID: <20090407171324.GB31824@shareable.org> (raw)
In-Reply-To: <49DB5AAE.8050205@codemonkey.ws>
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
next prev parent reply other threads:[~2009-04-07 17:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 2:37 Changing the QEMU svn VERSION string Anthony Liguori
2009-04-07 8:10 ` [libvirt] Re: [Qemu-devel] " Gerd Hoffmann
2009-04-07 9:03 ` Daniel Veillard
2009-04-07 13:52 ` Anthony Liguori
2009-04-07 17:13 ` Jamie Lokier [this message]
2009-04-08 6:35 ` Gerd Hoffmann
2009-04-07 17:58 ` [libvirt] " Daniel Jacobowitz
2009-04-07 22:36 ` [libvirt] Re: [Qemu-devel] " Paul Brook
2009-04-08 13:13 ` Anthony Liguori
2009-04-08 13:56 ` Jamie Lokier
2009-04-07 9:04 ` Daniel P. Berrange
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090407171324.GB31824@shareable.org \
--to=jamie@shareable.org \
--cc=kraxel@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=libvir-list@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=veillard@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.