[solved] ruby-vte error

Question

I'm the new owner of the package ruby-vte, the package creation is fine, but when I try a single test code:
#!/usr/bin/ruby
require 'gtk2'
require 'vte'
w = Gtk::Window.new
t = Vte::Terminal.new
w.set_title "Ruby Terminal"
w.signal_connect("destroy") do
Gtk.main_quit
end
t.signal_connect("child-exited") do
Gtk.main_quit
end
w.add t
w.show_all
Gtk.main
it returns this errors:
/usr/lib/ruby/2.1.0/rubygems/dependency.rb:298:in `to_specs': Could not find 'gtk2' (= 2.2.0) among 11 total gem(s) (Gem::LoadError)
from /usr/lib/ruby/2.1.0/rubygems/specification.rb:1295:in `block in activate_dependencies'
from /usr/lib/ruby/2.1.0/rubygems/specification.rb:1284:in `each'
from /usr/lib/ruby/2.1.0/rubygems/specification.rb:1284:in `activate_dependencies'
from /usr/lib/ruby/2.1.0/rubygems/specification.rb:1266:in `activate'
from /usr/lib/ruby/2.1.0/rubygems.rb:196:in `rescue in try_activate'
from /usr/lib/ruby/2.1.0/rubygems.rb:193:in `try_activate'
from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:132:in `rescue in require'
from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:144:in `require'
from test.rb:4:in `<main>'
I have this installed, query by pacman -Qs ruby
local/ruby 2.1.2-1
An object-oriented language for quick and easy programming
local/ruby-atk 2.2.0-1
Ruby bindings for atk
local/ruby-cairo 1.12.9-1
Ruby bindings for cairo
local/ruby-gdkpixbuf2 2.2.0-1
Ruby bindings for gdkpixbuf2
local/ruby-glib2 2.2.0-1
Ruby bindings for glib2
local/ruby-gtk2 2.2.0-1
Ruby bindings for gtk2
local/ruby-pango 2.2.0-1
Ruby bindings for pango
local/ruby-pkgconfig 1.1.5-1
Implementation of pkg-config in ruby
local/ruby-vte 2.2.0-2
Ruby bindings to VTE (gtk2)
any ideas?
Last edited by Joel (2014-08-16 00:55:38)

Answer 1

The reason I gave the response I did was that the forum is searchable through either the built in functions or an external site like Google.  Someone else who is having a similar issue, say six months from now, might stumble on this thread - which is marked [Solved] - and enter it looking for information that might pertain to the problem they themselves have.  The prescribed solution to this thread is to examine the PKGBUILD.  In six months time that PKGBUILD is likely to have changed rendering the future searcher back to square one.  This thread is an opportunity to document in plain English what went wrong and how it was actually resolved, instead there is a pointer to an evolving and likely not well commented PKGBUILD.