From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: gleb@qumranet.com
Subject: Re: [Qemu-devel] [PATCH 2/3]: Add -uuid option to Qemu
Date: Tue, 05 Aug 2008 16:32:54 +0200 [thread overview]
Message-ID: <48986496.90202@redhat.com> (raw)
In-Reply-To: <48985B63.8060506@redhat.com>
Chris Lalancette wrote:
> Gerd Hoffmann wrote:
>> Chris Lalancette wrote:
>>> As suggested by Anthony, this patch and the next one were split apart. This
>>> patch just adds the basic plumbing to qemu to be able to set the uuid on the
>>> command-line, and retrieve the information via "info uuid".
>> What is the point of CONFIG_UUID and the libuuid test in that patch?
>> I can't see any dependency on it in the source code. IMHO the -uuid
>> switch should be present unconditionally.
>
> Hm, CONFIG_UUID is used, for instance, to control whether we output the -uuid
> part of the help string. There are other uses in the patch as well.
Sure.
> I think the problem with including it unconditionally is that it drags in the
> uuid library, which may or may not always be available.
Does it? As far I can see none of the bits wrapped into #ifdef
CONFIG_UUID actually calls that library.
If you wanna do stuff like generating a uuid in case none was specified
on the command line, _then_ you'll need libuuid and those parts should
be compiled conditionally. I don't see the point for the -uuid cmd line
switch though.
Gleb's patches seem to have organized things this way according to his
reply (didn't check list archive).
cheers,
Gerd
--
http://kraxel.fedorapeople.org/xenner/
prev parent reply other threads:[~2008-08-05 14:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-28 13:25 [Qemu-devel] [PATCH 2/3]: Add -uuid option to Qemu Chris Lalancette
2008-08-05 13:43 ` Gerd Hoffmann
2008-08-05 13:53 ` Gleb Natapov
2008-08-05 14:36 ` Andreas Färber
2008-08-05 13:53 ` Chris Lalancette
2008-08-05 14:32 ` Gerd Hoffmann [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=48986496.90202@redhat.com \
--to=kraxel@redhat.com \
--cc=gleb@qumranet.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).