mcollective, rubygems and libstomp-ruby

Hi,

So the rubygems dependency makes me twitch since my servers can't do
gem installs from remote servers (for obvious reasons). I asked
upstream why it was required and he told me it was only really used by
the stomp plugin because "generally stomp is provided by gems".
Digging further, it turns out that if we had a remotely modern version
of libstomp-ruby, that'd be perfectly sufficient for mcollective and
we could drop the 'require rubygems' entirely (at least in our
packages). \o/

The newer version of libstomp-ruby issue is tracked here:

  https://bugs.launchpad.net/ubuntu/+source/libstomp-ruby/+bug/707317

(and http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598564)

So, once that (or something like it is merged), in terms of
mcollective, I think mcollective's dependency on libstomp-ruby should
be versioned to >= 1.1.9 and then we can drop the 'require rubygems'
and corresponding dependency?

--
James