From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hollis Blanchard Subject: Re: userspace repositories Date: Thu, 25 Oct 2007 14:01:03 -0500 Message-ID: <1193338863.28279.42.camel@basalt> References: <4720DC70.6090607@qumranet.com> <1193337447.28279.27.camel@basalt> <4720E312.3060400@qumranet.com> Reply-To: Hollis Blanchard Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, kvm-ppc-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org To: Avi Kivity Return-path: In-Reply-To: <4720E312.3060400-atKUWr5tajBWk0Htik3J/w@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org On Thu, 2007-10-25 at 20:40 +0200, Avi Kivity wrote: > Hollis Blanchard wrote: > > Avi, what do you think about breaking the kvm-userspace repository into > > separate kvm-qemu, kvmctl, and libkvm repositories? > > Firstly, I think kvmctl and libkvm should stay together. Why? As far as I can see, there are currently two independent consumers of libkvm: qemu and kvmctl. At the very least they should live in separate directories. Also, having libkvm on its own means that only one package has to include kernel headers and deal with that configure mess. The userspace apps really have no need for that... -- Hollis Blanchard IBM Linux Technology Center ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/