[opensuse-ruby] -rvendor-specific doesn't exist in ruby 1.9 in Factory
Hi All, The devel:languages:ruby:extensions/ruby-fcgi build is failing ATM because: Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.vtRX8Z ... + ruby -rvendor-specific install.rb config /usr/lib64/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- vendor-specific (LoadError) from /usr/lib64/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' Our ruby 1.8 supported -rvendor-specific, but 1.9 apparently does not. Do we need this? Or can I just get rid of the "-rvendor-specific" bits from the ruby-fcgi spec file? (I'm not familiar with this option...) Thanks, Tim -- Tim Serong Senior Clustering Engineer SUSE tserong@suse.com -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ruby+owner@opensuse.org
On 04.06.2012 11:40, Tim Serong wrote:
Hi All,
The devel:languages:ruby:extensions/ruby-fcgi build is failing ATM because:
Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.vtRX8Z ... + ruby -rvendor-specific install.rb config /usr/lib64/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- vendor-specific (LoadError) from /usr/lib64/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
Our ruby 1.8 supported -rvendor-specific, but 1.9 apparently does not. Do we need this? Or can I just get rid of the "-rvendor-specific" bits from the ruby-fcgi spec file?
(I'm not familiar with this option...)
Hi Tim, This is not an option, but -r pulls in another module. And vendor-specific was a module ruby 1.8 never had officially, we patched it. And this never took off upstream, I decided not to carry this over in 1.9. The idea behind vendor-specific is that it overwrites sitedir with vendordir if you call it. As this can't be used upstream, this only happens in our packages (and cmake very interestingly). Try just to drop it. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ruby+owner@opensuse.org
On 2012-06-04 11:44:00 +0200, Stephan Kulow wrote:
On 04.06.2012 11:40, Tim Serong wrote:
Hi All,
The devel:languages:ruby:extensions/ruby-fcgi build is failing ATM because:
Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.vtRX8Z ... + ruby -rvendor-specific install.rb config /usr/lib64/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- vendor-specific (LoadError) from /usr/lib64/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
Our ruby 1.8 supported -rvendor-specific, but 1.9 apparently does not. Do we need this? Or can I just get rid of the "-rvendor-specific" bits from the ruby-fcgi spec file?
(I'm not familiar with this option...)
Hi Tim,
This is not an option, but -r pulls in another module. And vendor-specific was a module ruby 1.8 never had officially, we patched it.
And this never took off upstream, I decided not to carry this over in 1.9.
The idea behind vendor-specific is that it overwrites sitedir with vendordir if you call it. As this can't be used upstream, this only happens in our packages (and cmake very interestingly).
Try just to drop it.
1. so instead of providing one little file to install things to vendor_ruby we will patch every single setup.rb to support a --vendor parameter? 2. another option would be of course to move all our own code into gems ... and install it that way. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ruby+owner@opensuse.org
On 04.06.2012 12:43, Marcus Rueckert wrote:
1. so instead of providing one little file to install things to vendor_ruby we will patch every single setup.rb to support a --vendor parameter?
Every single setup.rb of the two we have in factory, yes :)
2. another option would be of course to move all our own code into gems ... and install it that way.
ruby-fcgi is your package afaik. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ruby+owner@opensuse.org
On 06/04/2012 08:46 PM, Stephan Kulow wrote:
On 04.06.2012 12:43, Marcus Rueckert wrote:
1. so instead of providing one little file to install things to vendor_ruby we will patch every single setup.rb to support a --vendor parameter?
Every single setup.rb of the two we have in factory, yes :)
2. another option would be of course to move all our own code into gems ... and install it that way.
ruby-fcgi is your package afaik.
Actually, I've just realised we've also got rubygem-ruby-fcgi, which is newer than and obsoletes ruby-fcgi. So I guess I should probably deletereq ruby-fcgi from Factory and request rubygem-ruby-fcgi go in in its place? (removing -rvendor-specific from ruby-fcgi gets the build a bit further, but it then dies with errors like "'struct RString' has no member named 'ptr'" which I'll guess are 1.8/1.9 issues). Thanks, Tim -- Tim Serong Senior Clustering Engineer SUSE tserong@suse.com -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ruby+owner@opensuse.org
On 04.06.2012 12:52, Tim Serong wrote:
On 06/04/2012 08:46 PM, Stephan Kulow wrote:
On 04.06.2012 12:43, Marcus Rueckert wrote:
1. so instead of providing one little file to install things to vendor_ruby we will patch every single setup.rb to support a --vendor parameter?
Every single setup.rb of the two we have in factory, yes :)
2. another option would be of course to move all our own code into gems ... and install it that way.
ruby-fcgi is your package afaik.
Actually, I've just realised we've also got rubygem-ruby-fcgi, which is newer than and obsoletes ruby-fcgi. So I guess I should probably deletereq ruby-fcgi from Factory and request rubygem-ruby-fcgi go in in its place? That's what happened to e.g. ldap a while ago. And gem already knows about vendor support.
(removing -rvendor-specific from ruby-fcgi gets the build a bit further, but it then dies with errors like "'struct RString' has no member named 'ptr'" which I'll guess are 1.8/1.9 issues).
Yes, but those are easy to port. It's something around -R_STRING(thing)->ptr +R_STRING_PTR(thing) Greetings, Stephan -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ruby+owner@opensuse.org
On 06/04/2012 10:01 PM, Stephan Kulow wrote:
On 04.06.2012 12:52, Tim Serong wrote:
On 06/04/2012 08:46 PM, Stephan Kulow wrote:
On 04.06.2012 12:43, Marcus Rueckert wrote:
1. so instead of providing one little file to install things to vendor_ruby we will patch every single setup.rb to support a --vendor parameter?
Every single setup.rb of the two we have in factory, yes :)
2. another option would be of course to move all our own code into gems ... and install it that way.
ruby-fcgi is your package afaik.
Actually, I've just realised we've also got rubygem-ruby-fcgi, which is newer than and obsoletes ruby-fcgi. So I guess I should probably deletereq ruby-fcgi from Factory and request rubygem-ruby-fcgi go in in its place? That's what happened to e.g. ldap a while ago. And gem already knows about vendor support.
OK, I've submitted: https://build.opensuse.org/request/show/123591 (add rubygem-ruby-fcgi) https://build.opensuse.org/request/show/123592 (delete ruby-fcgi)
(removing -rvendor-specific from ruby-fcgi gets the build a bit further, but it then dies with errors like "'struct RString' has no member named 'ptr'" which I'll guess are 1.8/1.9 issues).
Yes, but those are easy to port. It's something around -R_STRING(thing)->ptr +R_STRING_PTR(thing)
Ah, fair enough. Still, my vote would be rubygem-ruby-fcgi as above - seems cleaner than fixing ruby-fcgi. Also, it's a slightly newer version, and the changelog actually mentions supporting ruby 1.9 :) Cheers, Tim -- Tim Serong Senior Clustering Engineer SUSE tserong@suse.com -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ruby+owner@opensuse.org
On 2012-06-04 14:01:32 +0200, Stephan Kulow wrote:
That's what happened to e.g. ldap a while ago. And gem already knows about vendor support.
wrong... vendor gem support is still on the agenda ... atm gems from rpms and manually installed gems end up in the same place. gem uninstall of rpmified gems also uninstalls those. there is an upstream discussion about this as it will be needed for gemified stdlib in the future. but no results yet iirc. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ruby+owner@opensuse.org
participants (3)
-
Marcus Rueckert -
Stephan Kulow -
Tim Serong