On 2006-10-04 16:48:27 +0200, Martin Vuk wrote:
One sidenote which probobally aims at ruby packagers.
Why is ruby sitelibdir (/usr/lib(64)/ruby/site_ruby/ ) arch specific? Is there a reason for packages containing only ruby source code to be architecture dependant?
because you cant create a noarch and arch dependent package in the same spec file. and i dont see the need in 2 spec files for that atm. while we are at it: for 10.2 i applied a patch that adds vendor_ruby to the lists of supported directories. the patch is already active in the ruby project in the buildservice. add "-rvendor-specific" to the cmdline, when calling extconf.rb/setup.rb/install.rb. for examples see the ruby project. additionally ... if your ruby library is provided as gem, you should package it as gem. (see rubygem-* packages) mostlikely another gem will depend on it. so having it as rubygem-* rpm makes it possible to use it from gems and use it directly from other libraries/scripts. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org