From: "Daniel P. Berrange" <berrange@redhat.com>
To: Anthony Liguori <aliguori@linux.vnet.ibm.com>
Cc: Jes Sorensen <Jes.Sorensen@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>,
clalance@redhat.com, qemu-devel@nongnu.org,
Cole Robinson <crobinso@redhat.com>
Subject: Re: [Qemu-devel] Re: [PATCH] Revive -version 'QEMU PC Emulator...'
Date: Fri, 14 May 2010 14:25:39 +0100 [thread overview]
Message-ID: <20100514132539.GG9282@redhat.com> (raw)
In-Reply-To: <4BED4D7E.50606@linux.vnet.ibm.com>
On Fri, May 14, 2010 at 08:17:50AM -0500, Anthony Liguori wrote:
> On 05/12/2010 03:48 PM, Cole Robinson wrote:
> >On 05/12/2010 04:38 PM, Jes Sorensen wrote:
> >
> >>On 05/12/10 22:29, Cole Robinson wrote:
> >>
> >>>Commit f75ca1ae205f24dae296c82d534c37746f87232f changed the version
> >>>string from:
> >>>
> >>>QEMU PC Emulator version x.yy.z
> >>>
> >>>to
> >>>
> >>>QEMU Emulator version x.yy.z
> >>>
> >>>libvirt is overly sensitive to the format of this string, and barfs when
> >>>trying to parse qemu -help output. While libvirt should certainly be more
> >>>robust here, changing the output format of -version for cosmetic reasons
> >>>doesn't seem like the best idea, so let's revert the change and add a
> >>>comment explaining the issue.
> >>>
> >>Rather than this, I would prefer a -version argument that just returns
> >>the current QEMU version string.
> >>
> >>IMHO it's not a good approach to do static string matching.
> >>
> >>
> >I agree libvirt's method is a crappy approach. Adding a proper -version
> >argument is certainly the way forward, but doesn't help users with
> >existing libvirt installations that want to use latest qemu. This is the
> >type of issue that libvirt devs will be fielding for months. Ideally i'd
> >like the order to be:
> >
> >1) Apply this patch
> >2) Add a proper -version argument, maybe named -version_num
> >3) libvirt patched to use new version argument (and robustify legacy
> >version parsing)
> >4) Some reasonable amount of time from now (6 months, a year?), edit the
> >current -version string at will
> >
> >I'd be willing to do 2 and 3 if people agree.
> >
>
> I'd like to see exactly what information libvirt needs so that we can
> agree on the proper interface to obtain it. My concern is that we'd
> have the same problem with the version string.
>
> This topic has come up many times in the past. We don't support the
> format of help output and libvirt shouldn't be using it. That's been
> expressed many, many times in the past and libvirt has not stopped using it.
We'd love to use something else, but since the 'something else' doesn't
yet exist we've had no choice but to continue groking the help output.
The discussion about a formally structure -query-version command is a step
in the right direction here. A similar option for querying supported command
line args would remove the need to rely on -help output.
Regards,
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://deltacloud.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
prev parent reply other threads:[~2010-05-14 13:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 20:29 [Qemu-devel] [PATCH] Revive -version 'QEMU PC Emulator...' Cole Robinson
2010-05-12 20:38 ` [Qemu-devel] " Jes Sorensen
2010-05-12 20:48 ` Cole Robinson
2010-05-13 8:35 ` Jes Sorensen
2010-05-13 13:04 ` Cole Robinson
2010-05-13 13:07 ` Jes Sorensen
2010-05-13 13:21 ` Daniel P. Berrange
2010-05-13 13:38 ` Luiz Capitulino
2010-05-13 14:00 ` Paul Brook
2010-05-13 19:20 ` Blue Swirl
2010-05-13 21:24 ` Stuart Brady
2010-05-14 13:24 ` Anthony Liguori
2010-05-14 13:54 ` Daniel P. Berrange
2010-05-14 14:22 ` Anthony Liguori
2010-05-14 14:42 ` Daniel P. Berrange
2010-05-14 14:52 ` Anthony Liguori
2010-05-14 15:02 ` Daniel P. Berrange
2010-05-14 15:08 ` Anthony Liguori
2010-05-14 13:17 ` Anthony Liguori
2010-05-14 13:25 ` Daniel P. Berrange [this message]
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=20100514132539.GG9282@redhat.com \
--to=berrange@redhat.com \
--cc=Jes.Sorensen@redhat.com \
--cc=aliguori@linux.vnet.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=clalance@redhat.com \
--cc=crobinso@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).