[ANN] Ruby-GNOME2 0.90.6

Desktop Ruby-Gnome 2
1

Hi,

The Ruby-GNOME2 project released Ruby-GNOME2 0.90.6:
Download ruby-gtk2-0.90.6.tar.gz (Ruby-GNOME 2)
Download ruby-gnome2-all-0.90.6.tar.gz (Ruby-GNOME 2)

=== Summary

  • Removed deprecated packages. They are in:
    Ruby-GNOME 2 download | SourceForge.net
    • Ruby/Bonobo
    • Ruby/BonoboUI
    • Ruby/GConf
    • Ruby/GNOME2
    • Ruby/GnomeCanvas
    • Ruby/GnomePrint
    • Ruby/GnomePrintUI
    • Ruby/GnomeVFS
    • Ruby/GtkGLExt
    • Ruby/GtkHTML2
    • Ruby/GtkSourceView
    • Ruby/Libart
    • Ruby/Libglade
    • Ruby/PanelApplet
  • ALl supported packages (including experimental packages)
    support RubyGems.
    • Ruby/ATK
    • Ruby/GdkPixbuf2
    • Ruby/GLib2
    • Ruby/GIO2
    • Ruby/GLib2
    • Ruby/GooCanvas
    • Ruby/GStreamer
    • Ruby/GTK2
    • Ruby/GtkMozEmbed
    • Ruby/GtkSourceView2
    • Ruby/Pango
    • Ruby/Poppler
    • Ruby/RSVG2
    • Ruby/VTE
  • All supported packages except the followin packages
    support also RubyGems that include Windows binary.
    • Ruby/Gstreamer
    • Ruby/GtkMozEmbed
    • Ruby/VTE

=== Changes

==== All

  • remove all deprecated packages.
    [Masaaki A.]
  • all supported packages support RubyGems.
    [Masaaki A.]

==== Ruby/GLib2

  • Imrpovements

    • add gnome2-raketask.rb that is a utility library to
      define Rake tasks for Ruby-GNOME2 packages.
      [Masaaki A., Kouhei S.]

  • Fixes

    • fix GType conversion.
      [Kouhei S.]
    • fix rcairo installed by RubyGems detection.
      [Masaaki A.]

==== Ruby/GIO2

  • Improvements
    • support GIO 2.26.
      [Nikolai W.]

==== Ruby/GStreamer

  • Improvements
    • add Gst::MissingURISourceMessage.
      [Vincent C., Kouhei S.]
    • support RubyGems.
      [Masaaki A.]

==== Ruby/Pango

  • Fixes
    • rename Pango::LayoutIter#at_last_line! to
      at_last_line? because at_last_line is a predicate
      method. (at_last_line! still exists for backward compatibility.)
      [mrkn, Kouhei S.]

==== Ruby/GtkMozEmbed

  • Improvements
    • support RubyGems.
  • Fixes
    • support “2.0b7” style module version. #3141244
      [reandr, Kouhei S.]
      [Masaaki A.]

==== Ruby/GooCanvas

  • Improvements
    • support RubyGems.
      [Masaaki A.]

==== Ruby/GtkSourceView2

  • Improvements
    • support RubyGems.
      [Masaaki A.]

==== Ruby/VTE

  • Improvements
    • support RubyGems.
      [Masaaki A.]

=== Thanks

  • Vincent C.
  • mrkn
  • reandr
  • Nikolai W.
  • Masaaki A.

Thanks,

kou

2

Hi kou

Is there a process for unremoving/undeprecating packages?

There was a discussion a long time ago about the fact that the
PanelApplet package was marked as deprecated. There really didn’t seem
to be any reason apart from the module having no designated
‘maintainer’. But as the code was working, there didn’t seem to be any
reason to remove it. Since that time, the PanelApplet code was updated
by Detlef R…

Has something changed that means the code stopped working? Is there
something new that needs to be done to it for gem support?

Regards
Grant

3

Hi,

In 1296427294.19957.97.camel@putnam
“Re: [ruby-gnome2-devel-en] [ANN] Ruby-GNOME2 0.90.6” on Mon, 31 Jan
2011 11:41:34 +1300,
Grant McLean [email protected] wrote:

Is there a process for unremoving/undeprecating packages?

  1. The package isn’t deprecated by the GTK+/GNOME team.
  2. We need an active maintainer for it.

There was a discussion a long time ago about the fact that the
PanelApplet package was marked as deprecated. There really didn’t seem
to be any reason apart from the module having no designated
‘maintainer’. But as the code was working, there didn’t seem to be any
reason to remove it. Since that time, the PanelApplet code was updated
by Detlef R…

No maintainer is a serious problem for us…
If our release includes a deprecated package and ithas a
bug, we will need to fix it. But we should work on supported
packages instead of deprecated packages. We only have
limited resources.

Has something changed that means the code stopped working? Is there
something new that needs to be done to it for gem support?

No. We still need just an active maintainer.

I’m sorry about our limited resources…

Thanks,

kou