Bug 789304 - Fix the binary extension placement
Summary: Fix the binary extension placement
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: rubygem-raindrops
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Guillermo Gómez
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-10 11:00 UTC by Vít Ondruch
Modified: 2012-06-15 10:14 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-15 10:14:52 UTC
Type: ---


Attachments (Terms of Use)

Description Vít Ondruch 2012-02-10 11:00:03 UTC
Hello,

Could you please update your .spec file according to the new guidelines for Ruby 1.9.1?

* If gem has binary extension, we are not placing it anymore into the site_archdir nor vendor_archdir but into %{gem_extdir}. Please see the guidelines [1] for more info.

* You can also use new macros such as %{gem_spec}, %{gem_cache}, but this is not crucial.

Thank you.


[1] https://fedoraproject.org/wiki/PackagingDrafts/Ruby#RubyGem_with_extension_libraries_written_in_C

Comment 1 Guillermo Gómez 2012-02-10 19:13:50 UTC
Thanks , really, i think i did better now.

* http://koji.fedoraproject.org/koji/taskinfo?taskID=3779982

Comment 2 Guillermo Gómez 2012-02-10 21:37:17 UTC
Ooops ! It builded right in mock f17 .. but it nows shows a dep problem generating the doc in koji... i'll review.

ERROR:  While generating documentation for raindrops-0.8.0
... MESSAGE:   cannot load such file -- irb/slex
... RDOC args: --ri --op /builddir/build/BUILD/rubygem-raindrops-0.8.0/usr/share/gems/doc/raindrops-0.8.0/ri -t raindrops - real-time stats for preforking Rack servers -W http://bogomips.org/raindrops.git/tree/%s lib README LICENSE NEWS ChangeLog lib/raindrops.rb lib/raindrops/aggregate.rb lib/raindrops/aggregate/last_data_recv.rb lib/raindrops/aggregate/pmq.rb lib/raindrops/last_data_recv.rb lib/raindrops/linux.rb lib/raindrops/middleware.rb lib/raindrops/middleware/proxy.rb lib/raindrops/struct.rb lib/raindrops/watcher.rb ext/raindrops/raindrops.c ext/raindrops/linux_inet_diag.c ext/raindrops/linux_tcp_info.c --title raindrops-0.8.0 Documentation
/usr/bin/install -c -m 0755 raindrops_ext.so /builddir/build/BUILD/rubygem-raindrops-0.8.0/usr/share/gems/gems/raindrops-0.8.0/lib
Successfully installed raindrops-0.8.0

Comment 3 Guillermo Gómez 2012-02-12 19:09:28 UTC
adding ruby-irb fixes this issue.

Comment 4 Vít Ondruch 2012-02-13 12:32:18 UTC
(In reply to comment #2)
> Ooops ! It builded right in mock f17 .. but it nows shows a dep problem
> generating the doc in koji... i'll review.
> 
> ERROR:  While generating documentation for raindrops-0.8.0
> ... MESSAGE:   cannot load such file -- irb/slex
> ... RDOC args: --ri --op
> /builddir/build/BUILD/rubygem-raindrops-0.8.0/usr/share/gems/doc/raindrops-0.8.0/ri
> -t raindrops - real-time stats for preforking Rack servers -W
> http://bogomips.org/raindrops.git/tree/%s lib README LICENSE NEWS ChangeLog
> lib/raindrops.rb lib/raindrops/aggregate.rb
> lib/raindrops/aggregate/last_data_recv.rb lib/raindrops/aggregate/pmq.rb
> lib/raindrops/last_data_recv.rb lib/raindrops/linux.rb
> lib/raindrops/middleware.rb lib/raindrops/middleware/proxy.rb
> lib/raindrops/struct.rb lib/raindrops/watcher.rb ext/raindrops/raindrops.c
> ext/raindrops/linux_inet_diag.c ext/raindrops/linux_tcp_info.c --title
> raindrops-0.8.0 Documentation
> /usr/bin/install -c -m 0755 raindrops_ext.so
> /builddir/build/BUILD/rubygem-raindrops-0.8.0/usr/share/gems/gems/raindrops-0.8.0/lib
> Successfully installed raindrops-0.8.0

Ups, that might be very well my issues, because I built new rubygem-rdoc package in the mean time, and that should requir ruby-irb. Have to check it out.

Comment 5 Vít Ondruch 2012-02-13 16:32:25 UTC
Sorry for any inconvenience. The problem with IRB was really on my side. rubygem-rdoc is fixed and ruby(irb) should not be needed anymore.

Comment 6 Vít Ondruch 2012-06-15 10:14:52 UTC
This was fixed already.


Note You need to log in before you can comment on or make changes to this bug.