[Slackbuilds-users] RFC: drop or merge qemu-kvm

Robby Workman rworkman at slackbuilds.org
Tue Feb 26 03:37:42 UTC 2013


On Mon, 25 Feb 2013 21:18:45 -0600
Robby Workman <rworkman at slackbuilds.org> wrote:

> On Mon, 25 Feb 2013 14:37:14 -0800
> King Beowulf <kingbeowulf at gmail.com> wrote:
> 
> > Since qemu-kvm devs have pushed the kvm bits upstream to qemu as of
> > 1.3, should we dropqemu-kvm? It does not appear that qemu-kvm will
> > be updated past 1.2 and qemu is now at 1.4.  That might make
> > installing both on the same system a bit tricky.
> 
> 
> Yes, it should be dropped - plan for that to occur unless there's
> serious objection.
> 
> In my experience with qemu (and I use it fairly often), I think the
> only thing we need to ensure that it still works with some other
> related stuff (e.g. aqemu) is a /usr/bin/qemu-kvm symlink pointing
> to /usr/bin/qemu-system-$ARCH (generally x86_64)


I'll do better even; here is (attached) the qemu build script I 
have been using.

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: qemu.tar.gz
Type: application/x-gzip
Size: 3040 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20130225/599d3e4d/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20130225/599d3e4d/attachment.asc>


More information about the SlackBuilds-users mailing list