On Fri, Mar 22, 2013 at 11:11:30AM +0100, Christophe Fergeau wrote:
> virtxml was doing its own loading of the libosinfo database,
> and gvir_designer_init() was loading it a second time.
> By adding a GVirDesignerDomain::osinfo_db property, applications
> can share the same OsinfoDb as libvirt-des
On Fri, Mar 22, 2013 at 11:22:20AM +0100, Michal Privoznik wrote:
> On 22.03.2013 11:11, Christophe Fergeau wrote:
> > virtxml was doing its own loading of the libosinfo database,
> > and gvir_designer_init() was loading it a second time.
> > By adding a GVirDesignerDomain::osinfo_db property, appl
On 22.03.2013 11:11, Christophe Fergeau wrote:
> virtxml was doing its own loading of the libosinfo database,
> and gvir_designer_init() was loading it a second time.
> By adding a GVirDesignerDomain::osinfo_db property, applications
> can share the same OsinfoDb as libvirt-designer. The associatio
virtxml was doing its own loading of the libosinfo database,
and gvir_designer_init() was loading it a second time.
By adding a GVirDesignerDomain::osinfo_db property, applications
can share the same OsinfoDb as libvirt-designer. The association
is made per libvirt-designer domain for more flexibil