On Wed, Jul 29, 2009 at 01:24:24PM +0200, Guido G?nther wrote: > On Wed, Jul 29, 2009 at 10:33:12AM +0100, Daniel P. Berrange wrote: > [..snip..] > > FYI, my libvirt-glib work is temporarily on hold due to lack of time. > > As such I've just pulled the event loop code directly into the > > virt-viewer application, so I can do a release of virt-viewer without > > needing to do a release of libvirt-glib right now. I want to pick it > > up again in the future and do something a little more advanced than > > just event loops, actually providing a proper GObject's for each libvirt > > objects so that GUI apps can just use normal GLib signal handling and > > properties, etc. virt-manager already does alot of this kind of wrapping > > in its own code, so its really pulling that out into a library where it > > can be shared > Sounds great! Will the old API still be there? I've just uploaded It will almost certainly change. This is reason I've not done any release of libvirt-glib - i didn't want to commit to this API as it is. That said there's only one public symbol there so far. Could do some evil linker script black magic to add compatibility for that Regards, Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| -- Libvir-list mailing list Libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list