From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12891] QEMU , libvirt-bin, qemu-kvm Package Support required
Date: Tue, 12 May 2020 05:26:15 +0000 [thread overview]
Message-ID: <bug-12891-163-IMQito42iZ@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12891-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=12891
--- Comment #1 from Tudor <tudor@tudorholton.com> ---
Package names are not consistent between projects. Sometimes, additional
"packages" are just extra options or additional libraries which are shipped as
separate binaries. Because buildroot builds the package from scratch they can
be shown as options and dependencies and therefore don't need additional
packages.
For example BR2_PACKAGE_QEMU_SYSTEM is the correct option for building what
other projects might call "qemu-system".
As such, we don't always need specific packages explicitly. Is there something
specifically you need from libvirt? From a buildroot perspective libvirt is a
bit redundant. Since you know categorically you'll be running on QEMU, why do
you need an abstraction layer? You don't need to jump from QEMU/KVM to Xen or
VMWare in a scratchbuilt environment like buildroot. You get that benefit by
being the designer of the environment.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-05-12 5:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 3:50 [Buildroot] [Bug 12891] New: QEMU , libvirt-bin, qemu-kvm Package Support required bugzilla at busybox.net
2020-05-12 5:26 ` bugzilla at busybox.net [this message]
2020-05-12 6:44 ` [Buildroot] [Bug 12891] " bugzilla at busybox.net
2020-05-12 11:55 ` bugzilla at busybox.net
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=bug-12891-163-IMQito42iZ@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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.