Miguel Gea Milvaques wrote: > * Package name : qemuctl
Are you aware that it has not seen any upstream development for eight months now? At least none that I know of. Did you contact the upstream? Alexander Schmehl wrote: > If it doesn't control qemu, could you avoid calling it so in the short > description? And maybe shou should also describe the difference to > qemu-launcher, so it is easier for our users to decide which of those > they want to install. In a perfect world, both. Qemuctl was designed to be used along with a GUI like Qemu Launcher. In reality it is a bit more hazy. While Qemu Launcher does include support for Qemuctl, it is hardly tested. The problem is that Qemu Launcher (v1.7+) contains support for features that Qemuctl does not (x86-64 support for example). This could be solved by merging both applications into a single suite. It would also allow for some fancy features that are likely to be implemented in Qemu Launcher 1.8 (already in progress). This is in my personal TODO list for quite some time, but other things just kept distracting me. Miguel Gea Milvaques wrote: > It's used from qemu-launcher, allowing suspend or reseting the vm. It's > *not* a qemu-launcher substitute, it works as a "plugin" for qemu-launcher. It is certainly a valuable addition to Qemu Launcher, but it is more useful as a stand-alone application in its current state. I am more that willing to cooperate on solving the issues. Just drop me a line or two regarding your plans. Regards, Linas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
