Bugzilla Bug 215149

The Ruby-Gnome2 set of packages currently has some packages stable at version
0.16.0 (the latest upstream version), and some packages stable at older
versions. In order to bring everything to 0.16.0, I'd like to ask for
stabilization of the following packages:

dev-ruby/ruby-gconf-0.16.0
dev-ruby/ruby-gnomeprint-0.16.0
dev-ruby/ruby-gnomeprintui-0.16.0
dev-ruby/ruby-gnomevfs-0.15.0
dev-ruby/ruby-gtkglext-0.16.0
dev-ruby/ruby-gtkhtml2-0.16.0
dev-ruby/ruby-gtkmozembed-0.16.0
dev-ruby/ruby-gtksourceview-0.16.0

Note that not all arches have all of these packages keyworded, and not all
arches may have any stable keyword yet. Please use your own judgement and arch
policy to determine how to handle this.

Sparc done, as follows:
  dev-ruby/ruby-gconf-0.16.0
  dev-ruby/ruby-gtkglext-0.16.0
  dev-ruby/ruby-gtkhtml2-0.16.0
are stable.

The others were not keyworded, but they mostly seem OK, and are all ~sparc.

NOTE:

USE=seamonkey FEATURES=test emerge -v ruby-gtkmozembed
FAILS, thus:
 * Failed Patch: ruby-gtkmozembed-0.15.0-seamonkey.patch !
Why?  Because the patch wants to do this to extconf.rb:
-PACKAGE_ID = "xulrunner-gtkmozembed"
+PACKAGE_ID = "seamonkey-gtkmozembed"

But what we have in ruby-gnome2-all-0.16.0/gtkmozembed/extconf.rb is:

 PACKAGE_IDS = ["xulrunner-gtkmozembed", 
               "firefox-gtkmozembed", 
               "mozilla-gtkmozembed"]

So the ~sparc for this package is rather conditional, and I don't think it can
go stable anywhere.

Ferris, thanks for the report on ruby-gtkmozembed. I've fixed the seamonkey
patch to work properly with 0.16.0 now.

ppc

=dev-ruby/ruby-gnomevfs-0.15.0
=dev-ruby/ruby-gtkglext-0.16.0

~ppc

=dev-ruby/ruby-gnomeprint-0.16.0
=dev-ruby/ruby-gnomeprintui-0.16.0
=dev-ruby/ruby-gtkhtml2-0.16.0
=dev-ruby/ruby-gtkmozembed-0.16.0
=dev-ruby/ruby-gtksourceview-0.16.0

alpha/ia64 stable

Fails:
dev-ruby/ruby-gtksourceview-0.16.0

# ruby /usr/share/doc/ruby-gtksourceview-0.16.0/sample/test
test.rb:21: undefined method `tags' for nil:NilClass (NoMethodError)

which is _very_ funny because if you edit test.rb and
s:text/x-ruby:text/x-python: it works!

------------------------------

Apart from that...

I haven't been able to test properly yet (amd64 people, help!):
dev-ruby/ruby-gnomevfs-0.15.0
dev-ruby/ruby-gtkglext-0.16.0
dev-ruby/ruby-gtkmozembed-0.16.0 (it looks ok for stable, but have to test with
seamonkey)

amd64 stable for:
dev-ruby/ruby-gconf-0.16.0
dev-ruby/ruby-gnomeprint-0.16.0
dev-ruby/ruby-gnomeprintui-0.16.0 (and quoting fixed)
dev-ruby/ruby-gtkhtml2-0.16.0

x86 stable

@ruby: ping? any advice on dev-ruby/ruby-gtksourceview problem?

The gtksourceview issue isn't a real bug. It looks like gtksourceview-1 only
can handle a single mime type per language, and the ruby file has
application/x-ruby, while the python file has text/x-python. 

gtksourceview-2 has this solved with a more extensive mime-types property, but
this is not supported by gtksourceview, as far as I know.

(In reply to comment #5)
> I haven't been able to test properly yet (amd64 people, help!):
> dev-ruby/ruby-gnomevfs-0.15.0
> dev-ruby/ruby-gtkglext-0.16.0
> dev-ruby/ruby-gtkmozembed-0.16.0 (it looks ok for stable, but have to test with
> seamonkey)

amd64 stable for these packages. only remaining package should be
gtksourceview.

(In reply to comment #8)
> The gtksourceview issue isn't a real bug. It looks like gtksourceview-1 only
> can handle a single mime type per language, and the ruby file has
> application/x-ruby, while the python file has text/x-python. 
> 


Then what about patching the test program substituting text/x-ruby with
application/x-ruby ?

(In reply to comment #10)
> (In reply to comment #8)
> > The gtksourceview issue isn't a real bug. It looks like gtksourceview-1 only
> > can handle a single mime type per language, and the ruby file has
> > application/x-ruby, while the python file has text/x-python. 
> > 
> 
> 
> Then what about patching the test program substituting text/x-ruby with
> application/x-ruby ?
> 

Talked to Hans in irc and the ruby team would rather work on the next
ruby-gnome2 release. Nothing else blocks stablization, so mark it stable and
close this old bug.

Done.

All stable for sparc.