From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: Split kvm source tarballs Date: Wed, 25 Mar 2009 08:18:14 -0500 Message-ID: <49CA2F16.1070905@codemonkey.ws> References: <49C64963.20601@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: KVM list To: Avi Kivity Return-path: Received: from mail-qy0-f118.google.com ([209.85.221.118]:65072 "EHLO mail-qy0-f118.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753508AbZCYNST (ORCPT ); Wed, 25 Mar 2009 09:18:19 -0400 Received: by qyk16 with SMTP id 16so30872qyk.33 for ; Wed, 25 Mar 2009 06:18:17 -0700 (PDT) In-Reply-To: <49C64963.20601@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: Avi Kivity wrote: > As part of the preparations for a formal maintenance branch, we're now > providing userspace-only source tarballs and kernel module-only source > tarballs. The combined kernel/userspace package is still provided. > > Userspace package names will take the form 'qemu-kvm-devel-xx'. > Kernel module package names will take the form 'kvm-kmod-devel-xx'. > The combined package is named, as usual, kvm-xx'. > > When maintenance branch packages become available, -devel will be > dropped, of course. Only the split packages will be available for the > maintenance branch. > > The userspace package can run against modules from the matching kernel > module package, or against modules from a released Linux kernel > (version 2.6.25 or higher). In almost all cases, you can mix and > match userspace and kernel -devel packages. > > Please test the release candidates in > http://userweb.kernel.org/~avi/kvm-85rc1/ for any packaging errors. > Suggestions of any kind are also welcome. Hrm, I notice that for qemu-kvm, you basically just pulled out the module source. What do you think about going a step further and building a proper qemu repository? Regards, Anthony Liguori