I would call the following reasonable speculation of mine (unchecked yet in actual reality):
Any installer probably expects (a set of or at least one) meta package. So if we had a meta package Whonix host, that would help the installer. We’ll need such a meta package either way.
To have fewer special cases in the Whonix source code, i.e. to not have
- A) some packages, and plus on top
- B) have some extra files(qcow2 images) / scripts (copy qcow2 images)
I had the idea to put the qcow2 files into a deb package (in this post: [Help Welcome] KVM Development - staying the course - #287 by Patrick) Would that be sane/good?
From a design perspective I think we might also get
sudo apt-get install whonix-host-kvm-xfce [1]
(to be run on Debian hosts, in theory)
(almost) effortless.
(Whether we want to / whether it is sane to support the sudo apt-get install whonix-host-kvm-xfce way of installation is a separate question.)
This would look to be like a clean, solid design.
[1] not sure in which order the name, getting a lot: host vs VM, kvm vs virtualbox, xfce vs cli