I'm about to reorder yet again qemu.

Before the idea was to provide just a single ebuild, qemu, covering it all.

The problem is that on a side we have the softmmu, full
emulator/paravirt that uses lots of libraries and has qemu-kvm sporting
some speedups over it from time to time; on the other we have qemu-user,
that doesn't have dipendencies and usually needs to be built statically.

qemu-user is nowadays widely used to have non-native chroot to speed up
building by overcoming non-cross-friendly build systems (hi
perl&python). With the patchset Fabio managed to put together we don't
even need to mess with hybrid systems due some key component for
building a recent desktop (e.g. cmake for kde) uncover bugs in the
machinery the hard way.

I'd add a new ebuild for qemu-user that is always static, with a
initscript to ease having the binfmt set up, it will be close
resembiling the ebuild qemu-user-static from sabayon and not colliding
with qemu.

Is anybody against to this approach?

lu

-- 

Luca Barbato
Gentoo/linux
http://dev.gentoo.org/~lu_zero


Reply via email to