Re: gem'izing ruby-gnome2-*?

[Thomas Klausner <wiz%NetBSD.org@localhost>]

On Thu, Jan 14, 2016 at 12:12:53AM +0900, Izumi Tsutsui wrote:
> wiz@ wrote:
> 
> > For that reason I've already converted two packages (locally) to
> > switch to the gem version. Now I found the error above, and see about
> > 15 ruby-gnome2 packages that do not install the gem.
> > 
> > Is there a particular reason for that, or can I switch them to gems?
> 
> It looks just because it they were imported before they were gem'fied.
> 
> mikutter works fine with the following gem'ized packages:
>  ruby200-gnome2-pango-3.0.7
>  ruby200-gnome2-atk-3.0.7
>  ruby200-gnome2-gobject-introspection-3.0.7
>  ruby200-gnome2-glib-3.0.7
>  ruby200-gnome2-gio-3.0.7
>  ruby200-gnome2-gdkpixbuf-3.0.7
>  ruby200-gnome2-gtk-3.0.7
> 
> (I should notice it before trying to update ruby-gnome2 to 3.0.7...)

Do I understand correctly: you have gem'ized the packages you mention
above?

If yes, can you please commit that?

> I wonder if we should keep PKGNAMEs for these packages and
> ruby-rcairo etc. (ruby-gnome2-glib needs glib2.gem for example)

Hm, I changed the name for ruby-rcairo to ruby-cairo to match the gem
name. I think this is easier to handle in the future than to stay with
old names forever...
 Thomas