On Tue, Mar 11, 2014 at 11:05:34 +0100, Jiri Denemark wrote:
On Mon, Mar 10, 2014 at 12:31:00 -0600, Eric Blake wrote:
On 03/10/2014 09:26 AM, Jiri Denemark wrote:
When libvirtd is run from a build directory without being installed, it
should not depend on files from a libvirt package
On Mon, Mar 10, 2014 at 12:31:00 -0600, Eric Blake wrote:
On 03/10/2014 09:26 AM, Jiri Denemark wrote:
When libvirtd is run from a build directory without being installed, it
should not depend on files from a libvirt package installed in the
system. Not only because there may not be any
When libvirtd is run from a build directory without being installed, it
should not depend on files from a libvirt package installed in the
system. Not only because there may not be any libvirt installed at all.
We already do a good job for plugins but cpu_map.xml was still loaded
from the system.
On Mon, Mar 10, 2014 at 04:26:30PM +0100, Jiri Denemark wrote:
When libvirtd is run from a build directory without being installed, it
should not depend on files from a libvirt package installed in the
system. Not only because there may not be any libvirt installed at all.
We already do a good
On 03/10/2014 09:26 AM, Jiri Denemark wrote:
When libvirtd is run from a build directory without being installed, it
should not depend on files from a libvirt package installed in the
system. Not only because there may not be any libvirt installed at all.
We already do a good job for plugins
