Ruby Forum Ruby-Gnome 2 > [ANN] Ruby-GNOME2-0.17.0-rc1

Posted by Joachim Glauche (joaz)
on 06.06.2008 16:28
Hi,

After a long long time, RC1 of Ruby-Gnome 0.17.0 is out!

Release notes:
  * This Release Candidate seems to be pretty stable. Please give us
    feedback if you encounter any problems.
  * The win32 bindings will be released later and will be considered as
EXPERIMENTAL
          The changes marked with 2 stars (**) may currently not work on
win32 platforms.

You can grab it here:
https://sourceforge.net/project/showfiles.php?group_id=53614&package_id=48093&release_id=604950

md5sum:
6d04af04c8674b0a88ce47e09dd26a76  ruby-gnome2-0.17.0-rc1.tar.gz

Quick install guide:
 tar -vxzf ruby-gnome2-0.17.0-rc1.tar.gz
 cd ruby-gnome2-0.17.0-rc1
 ruby exconf.rb
 make
 (sudo) make install

See README for extconf.rb options.


Main changes:
  * Ruby/GLib:
    - Bound functions defined since 2.14 and 2.16.
    - Improved main loop polling. **
    - Improved callback handling from non Ruby thread. **

      This changes breaks API. Sjoerd, you need to call
      rbgutil_start_callback_dispatch_thread() in your
      GStreamer bindings. Sorry.

    - Supported convenience GEnum and GFlags notation. e.g.:
        GLib::UTF8.normalize(utf8, GLib::NormalizeMode::NFD)
        ->
        GLib::UTF8.normalize(utf8, :nfd)

        key_file.load_from_data(data,
                                GLib::KeyFile::KEEP_COMMENTS |
                                GLib::KeyFile::KEEP_TRANSLATIONS)
        ->
        key_file.load_from_data(data, [:keep_contents,
:keep_translations])

    - Fixed locale dependent constant name computation. [#1901843]
      [Kouhei Sutou]

  * Ruby/GTK:
    - partially support new symbols in 2.12 (Gtk::RecentAction,
Gtk::TextBuffer,
      Gdk::Display, Gtk::TreeViewColumn, Gtk::Stock, Gtk::Widget,
Gtk::ScaleButton,
      Gtk::TreeView, Gtk::VolumneButton, Gtk::Tooptip and Gtk::TextMark
only).

  * Ruby/GStreamer: Worked with GStreamer >= 0.10.x but isn't
    completed yet.

  * Ruby/Poppler
    - Supported poppler-glib 0.6.x and 0.8.0. [Kouhei Sutou]

  * Ruby-GNOME2 can be built with ruby 1.9.0 but doesn't
    work well without [ruby-dev:34104] patch.

  * Some extconf.rb improvements

  * Many other changes, GC bugs, Segfault fixes. See corresponding
ChangeLog
    for detailed information on changes and contributors.

    Special thanks for your contributions to: (list in no particular
order)
    - Kazuhiro NISHIYAMA
    - Kouhei Sutou
    - Kero van Gelder
    - Masahiro Sakai
    - Detlef Reichl
    - Guillaume Cottenceau
    - Masahiro Sakai
    - Mikael Hallendal
    - Carlo E. Prelz
    - Sjoerd Simons
    - Juergen Mangler
    - Dirk von Schmieden
    - Mathieu Blondel
    - Joseph Method
    - Masayuki Yamaguchi

  And also special thanks to all other contributors not listed above!


Regards,
  Joachim Glauche
Posted by Jan Moren (Guest)
on 06.06.2008 16:52
(Received via mailing list)
Congrats!

Just one question: installing in this manner will replace the current
stable version? Is there a way to install the rc1 release without
breaking alredy installed Ruby-gnome or Ruby-GTK applications?


fre 2008-06-06 klockan 16:28 +0200 skrev Joachim Glauche:
> win32 platforms.
>  ruby exconf.rb
>     - Improved callback handling from non Ruby thread. **
>         key_file.load_from_data(data,
>     - partially support new symbols in 2.12 (Gtk::RecentAction,
>     - Supported poppler-glib 0.6.x and 0.8.0. [Kouhei Sutou]
>     Special thanks for your contributions to: (list in no particular
>     - Sjoerd Simons
>   Joachim Glauche
--
Jan Morén
Japan:  090-3622 8920
http://janneinosaka.blogspot.com
Posted by Joachim Glauche (joaz)
on 06.06.2008 17:07
Jan Moren wrote:
> Congrats!
> 
> Just one question: installing in this manner will replace the current
> stable version? Is there a way to install the rc1 release without
> breaking alredy installed Ruby-gnome or Ruby-GTK applications?

Yes the installation will overwrite the old version. I think the easiest 
way is to  re-install the old version (which also overwrites the current 
one) in case it doesn't work for you.

Joachim
Posted by Kouhei Sutou (Guest)
on 07.06.2008 01:17
(Received via mailing list)
Hi,

In <1212763850.5919.27.camel@mocha>
  "Re: [ruby-gnome2-devel-en] [ANN] Ruby-GNOME2-0.17.0-rc1" on Fri, 06 
Jun 2008 23:50:50 +0900,
  Jan Moren <janne@mx5.canvas.ne.jp> wrote:

> Just one question: installing in this manner will replace the current
> stable version? Is there a way to install the rc1 release without
> breaking alredy installed Ruby-gnome or Ruby-GTK applications?

What about 'make DESTDIR=/... install'?


Thanks,
--
kou
Posted by Joachim Glauche (joaz)
on 07.06.2008 16:16
Kouhei Sutou wrote:
>> Just one question: installing in this manner will replace the current
>> stable version? Is there a way to install the rc1 release without
>> breaking alredy installed Ruby-gnome or Ruby-GTK applications?
> 
> What about 'make DESTDIR=/... install'?

I think the makefiles need some improvements. It would be nice to be 
able to configure that with extconf.rb

I also noticed that adding -jX option to make does not have any effect 
in top level directories, while it is  seems to work fine if I go inside 
a src directory.
Posted by Kouhei Sutou (Guest)
on 08.06.2008 04:56
(Received via mailing list)
Hi,

In <31b372cac7f27fba75a3d6968418f920@ruby-forum.com>
  "Re: [ruby-gnome2-devel-en] [ANN] Ruby-GNOME2-0.17.0-rc1" on Sat, 7 
Jun 2008 16:16:06 +0200,
  Joachim Glauche <ruby-forum-incoming@andreas-s.net> wrote:

> Kouhei Sutou wrote:
> >> Just one question: installing in this manner will replace the current
> >> stable version? Is there a way to install the rc1 release without
> >> breaking alredy installed Ruby-gnome or Ruby-GTK applications?
> > 
> > What about 'make DESTDIR=/... install'?

> I also noticed that adding -jX option to make does not have any effect 
> in top level directories, while it is  seems to work fine if I go inside 
> a src directory.

I've fixed the problem. Could you try again?


Thanks,
--
kou
Posted by Joachim Glauche (joaz)
on 09.06.2008 14:42
Kouhei Sutou wrote:

> I've fixed the problem. Could you try again?

Hi Kou,

yes, works fine.

Thanks,
 Joachim