qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Jamie Lokier <jamie@shareable.org>
Cc: libvir-list@redhat.com, qemu-devel@nongnu.org,
	kvm-devel <kvm@vger.kernel.org>
Subject: Re: [libvirt] Re: [Qemu-devel] Changing the QEMU svn VERSION string
Date: Wed, 08 Apr 2009 08:35:09 +0200	[thread overview]
Message-ID: <49DC459D.1070909@redhat.com> (raw)
In-Reply-To: <20090407171324.GB31824@shareable.org>

On 04/07/09 19:13, Jamie Lokier wrote:
> 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.

Fedora typically handles this using a leading zero in the 'release' 
component for pre-final versions, like this: app-1.2.3-0.rc1.fc11 
(rc/beta) and app-1.2.3-1.fc11 (final).  Likewise for snapshots: 
app-1.2.3-0.svn${date}.fc11

> 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.

libvirt scans the help text to figure which features are present 
(checking for as -drive and -uuid cmd line switches for example).

cheers,
   Gerd

  reply	other threads:[~2009-04-08  6:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-07  2:37 [Qemu-devel] Changing the QEMU svn VERSION string Anthony Liguori
2009-04-07  8:10 ` Gerd Hoffmann
     [not found]   ` <20090407090322.GC31447@redhat.com>
2009-04-07 13:52     ` [libvirt] " Anthony Liguori
2009-04-07 17:13       ` Jamie Lokier
2009-04-08  6:35         ` Gerd Hoffmann [this message]
2009-04-07 17:58       ` Daniel Jacobowitz
2009-04-07 22:36         ` Paul Brook
2009-04-08 13:13           ` Anthony Liguori
2009-04-08 13:56           ` Jamie Lokier
2009-04-07  9:04 ` [Qemu-devel] " Daniel P. Berrange
2009-04-07 16:09 ` [Qemu-devel] " Andreas Färber
2009-04-07 16:29   ` M. Warner Losh
2009-04-08 21:10     ` Andreas Färber

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=49DC459D.1070909@redhat.com \
    --to=kraxel@redhat.com \
    --cc=jamie@shareable.org \
    --cc=kvm@vger.kernel.org \
    --cc=libvir-list@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).