The ruby bindings for gnome2 have been updated to 0.13. Although gnome itself is in the progress of 'leveling up' :) having these bindings as ebuilds would be handy. I found that just copying the 0.12.0 ebuilds to 0.13.0 works. This works for all ruby-gnome2-ish ebuilds except for ruby-gstreamer. At least for me :) I tested copying 0.12.0 to 0.13.0 works for ruby-pango ruby-libglade2 ruby-libart2 ruby-gtkhtml2 ruby-gtkglext ruby-gtk2 ruby-gnomevfs ruby-gnomecanvas2 ruby-gnome2 ruby-glib2 ruby-gdkpixbuf2 ruby-gconf2 and ruby-gstreamer. As said, it works for all but ruby-gstreamer. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 68694 [details] updated ebuilds for the 0.13 version Attached you will find all the ruby-gnome2-0.13 version ebuilds. You will also notice that for the ruby-gnomecanvas2-0.13 ebuild there is a patch applied. This patch comes from http://sourceforge.net/tracker/index.php?func=detail&aid=1287758&group_id=53614&atid=470969 and corrects a bug when using ruby-gnomecanvas2-0.13 under Gnome 2.12
By the way... ruby-gstreamer-0.13 emerge for me. But I'm using media-libs/gstreamer-0.8.11. Maybe it comes from that?
I'll try to finally commit this over the next few days. Thanks for the submissions!
Well, I never came around to actually finish this bump, last but not least because I ran into problems with certain packages. Now that ruby-gnome-0.14.0 is out (bug #109641), I see no point in finishing the ebuilds for 0.13.0. Unfortunately I won't time for this bump as I'm currently busy with other stuff...
ruby-gnome2-0.14.1 (released yesterday) has finally been commited to the tree. Sorry for the delay!
Grand! Now if there would just be ~amd64 flags for those packages... (Some of them are already done, some aren't, like ruby-gtksourceview, gtkglarea and gtkhtml2)
Explanation: when doing version bumps, all current arch keywords get dropped back to ~arch. For a new package, your only allowed to add in keywords for arches you can test on. I only own x86 machines, hence the new ebuilds are only keyworded ~x86. If you want to get them keyword for your architecture, just file a bug for the corresponding arch team.
Okay, didn't know that. Will do! Thanks!
