Yesterday, version 0.9.1 of ruby-gnome2 was released. And I made ebuild files and succeeded to emerge. However, I don't use the GNOME, but XFCE4, I made only the ruby-gtk2 package (Ruby/Glib2, Ruby/ATK, Ruby/GdkPixbuf2, Ruby/Pango, Ruby/GTK2). Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 27394 [details] ebuild of Ruby/Glib2 0.9.1
Created attachment 27395 [details] ebuild of Ruby/ATK 0.9.1
Created attachment 27396 [details] ebuild of Ruby/Ruby/GdkPixbuf2 0.9.1
Created attachment 27397 [details] ebuild of Ruby/Pango 0.9.1
Created attachment 27398 [details] ebuild of Ruby/GTK2 0.9.1
Thanks, version 0.9.1 is now in the tree. Why did you attach ebuilds with no changes? It's confusing, unhelpful and a waste of space. It would have been sufficient to say you renamed the ebuilds for the new version and it worked.
Reopening. How about doing a simple test before releasing ebuilds? The released ebuilds are incomplete. Anything requiring gtk2 will not work because ruby-atk has not been added to portage. File /usr/lib/ruby/site_ruby/1.8/gtk2.rb: 1> require 'glib2' 2> require 'atk' Takayuki provided the ebuild for ruby-atk and made gtk2 depend on it. The most basic test using any of the provided samples would have revealed the missing bit.
Yep, Xavier, you're right regarding testing. I also should have asked the poster if there were differences in the ebuilds he posted that I should be aware of. My bad. This is fixed in the tree now and I've done some basic testing. Thanks.