libvirt users - Mar 2011 - ruby bindings has two gems (I think)

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?

-jb
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://listman.redhat.com/archives/libvirt-users/attachments/20110310/87435b4e/attachment.htm>

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