Dear QEMU Developers, I'm writing to ask about the feasibility of including a script within a *closed-source application* that automates the installation of QEMU from standard Linux distribution repositories (e.g., *APT, RPM, Zypper, Pacman*).
My aim is to simplify the user experience by offering a convenient way for them to install QEMU, which is a key dependency for my application. I'm unsure if providing such a script would be considered "distributing" QEMU itself, or if it falls under a different category that would necessitate me building a custom QEMU version. Could you please clarify if this approach is permissible under QEMU's licensing and development guidelines? If it's not, could you advise on the recommended way to handle QEMU as a dependency for a closed-source application without requiring me to build a custom version (as I currently lack the expertise to do so)? Thanks for your time and guidance. Sincerely, Waissou murad waissoumu...@gmail.com
