Thanks for the info. Are there any plans to extend the functionality of the ruby-libvirt gem beyond just the bindings? For instance, convenience functions, OVF parsing, etc? We have needed this functionality so ended up building a gem called "ovfparse" for fetching and parsing these types of files (code at https://github.com/ruby-ovf/ovfparse).
-jb On Fri, Mar 11, 2011 at 4:15 PM, Chris Lalancette <clala...@redhat.com>wrote: > On 03/10/11 - 07:19:53PM, James Barkley wrote: > > When I look at remote gems I see: > > > > - libvirt (0.2.0), "A ruby client library providing an interface to > libvirt > > via FFI" > > - ruby-libvirt (0.3.0), "Provides bindings for libvirt" > > > > I've been using ruby-libvirt, but maybe I should give libvirt a try? Has > > anyone used libvirt (0.2.0) and developed opinions they'd like to share? > > I'm biased since I am the maintainer of ruby-libvirt, but I think > you should stick with ruby-libvirt :). I do more active maintenance of the > bindings than what I saw in the "libvirt" gem, and since I monitor the > libvirt > list I keep a very up-to-date with what is going on. The downside is that > if you are using anything but MRI, the ruby-libvirt bindings won't work. > Since > most people are not, this is not usually an issue, but it is something to > consider. > > -- > Chris Lalancette >
_______________________________________________ libvirt-users mailing list libvirt-users@redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users
