[kvm-devel] userspace repositories

2007-10-25 Thread Hollis Blanchard
Avi, what do you think about breaking the kvm-userspace repository into
separate kvm-qemu, kvmctl, and libkvm repositories?

-- 
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/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel


Re: [kvm-devel] userspace repositories

2007-10-25 Thread Avi Kivity
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.

I'm not thrilled about breaking up the repositories even more; it makes 
bisecting more difficult.  Perhaps git's module support can help here.


-- 
error compiling committee.c: too many arguments to function


-
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/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel


Re: [kvm-devel] userspace repositories

2007-10-25 Thread Hollis Blanchard
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/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel


Re: [kvm-devel] userspace repositories

2007-10-25 Thread Avi Kivity
Hollis Blanchard wrote:
 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.

   

They're both small, and tied up together.  I'd rather support one small 
package than two small packages.

Agree about 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...
   

kvmctl is intended to be a small test driver, no more.

-- 
error compiling committee.c: too many arguments to function


-
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/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel