From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Fourhundred Thecat <400thecat@gmx.ch>
Cc: "Michael Tokarev" <mjt@tls.msk.ru>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
qemu-discuss@nongnu.org, qemu-devel@nongnu.org
Subject: Re: qemu-system-x86 dependencies
Date: Thu, 17 Aug 2023 08:29:46 +0200 [thread overview]
Message-ID: <6db6de64-224f-40eb-a371-cdb71bfaa493@molgen.mpg.de> (raw)
In-Reply-To: <75824b67-6192-a1c2-b89c-b67818ffb08b@gmx.ch>
Dear Fourhundred,
Am 17.08.23 um 07:10 schrieb Fourhundred Thecat:
> > On 2023-08-16 15:02, Fourhundred Thecat wrote:
>> > On 2023-08-16 14:52, Michael Tokarev wrote:
>>> 16.08.2023 15:37, Philippe Mathieu-Daudé пишет:
>>>> Cc'ing Michael
>>>>
>> why does qemu depend on sound and gstreamer and wayland libraries?
>> After all, i am just trying to run VMs on my hypervisor.
>>
>> If I remember correctly, my previous installation on Debian 10,
>> qemu-system-x86 had no such dependencies.
>>
>> Seems to me like trying to install openssh-server, but it needs full
>> gnome environment libraries.
>
> sorry if my question offended people.
>
> Perhaps there is a good reason for these dependencies, which i don't see?
>
> Also, I am told that Arch has split all these into separate packages:
>
> https://archlinux.org/packages/?sort=&repo=Extra&q=qemu&maintainer=&flagged=
>
> So it looks like my original question might be Debian specific?
Please tell us, how you actually build QEMU (in the past). Building QEMU
from upstream sources and configuring it with minimal options, why do
the dependencies from the Debian package matter at all?
Kind regards,
Paul
next prev parent reply other threads:[~2023-08-17 6:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ed59d5cc-587e-ae8a-f367-96e4e58b67ce@gmx.ch>
2023-08-16 12:37 ` qemu-system-x86 dependencies Philippe Mathieu-Daudé
2023-08-16 12:52 ` Michael Tokarev
2023-08-16 13:02 ` Fourhundred Thecat
2023-08-17 5:10 ` Fourhundred Thecat
2023-08-17 6:29 ` Paul Menzel [this message]
2023-08-17 7:08 ` Michael Tokarev
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=6db6de64-224f-40eb-a371-cdb71bfaa493@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=400thecat@gmx.ch \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=qemu-discuss@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).