From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel@nongnu.org, kvm-devel <kvm@vger.kernel.org>,
Dustin Kirkland <kirkland@canonical.com>
Subject: [Qemu-devel] Re: [ANNOUNCE] qemu-kvm-0.12.0-rc2 released
Date: Tue, 15 Dec 2009 08:29:02 -0600 [thread overview]
Message-ID: <4B279D2E.5070001@codemonkey.ws> (raw)
In-Reply-To: <4B27529E.6050806@redhat.com>
Avi Kivity wrote:
> On 12/14/2009 11:58 PM, Dustin Kirkland wrote:
>>
>> I'm working on the packaging updates for Ubuntu Lucid, and I'm having
>> trouble with the BIOS bits of qemu-kvm.
>>
>> It seems that a fair amount of the BIOS submodules are missing.
>>
>> The roms/ tree is basically empty.
>>
>>
>
> Well, binaries are shipped, but I guess you'd like to build from source.
>
> We have several options:
>
> - do nothing
> - ship a generated SOURCES file which contains git URLs and commit
> hashes, rely on the interested user to fetch and build. Also tag the
> submodules appropriately.
> - fetch the submodules and include them in the tarball
I was thinking of taking this approach.
As we integrate the build environments, this will allow a user to do a
make and it will build all of the roms from source by default.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-12-15 14:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4B2684EC.2040504@redhat.com>
2009-12-14 21:58 ` [Qemu-devel] Re: [ANNOUNCE] qemu-kvm-0.12.0-rc2 released Dustin Kirkland
2009-12-15 9:10 ` Avi Kivity
2009-12-15 14:23 ` Lennart Sorensen
2009-12-15 14:29 ` Anthony Liguori [this message]
2009-12-15 15:21 ` Dustin Kirkland
2009-12-18 4:51 ` Dustin Kirkland
2009-12-20 16:25 ` Avi Kivity
2009-12-21 3:39 ` Dustin Kirkland
2009-12-21 9:30 ` Avi Kivity
[not found] ` <4B2748B6.9080305@eseco.de>
2009-12-15 9:07 ` Avi Kivity
2009-12-15 14:31 ` Anthony Liguori
2009-12-15 14:41 ` Gerd Hoffmann
2009-12-15 18:22 ` Luiz Capitulino
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=4B279D2E.5070001@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=kirkland@canonical.com \
--cc=kvm@vger.kernel.org \
--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).