(Improper?) usage of {rubylibdir, archdir} and {sitelibdir, sitearchdir} in 3rd ruby packages

[Tomasz Wittner]

Is there any reason that most of ruby packages put their files into ruby 
"system directories" - please, glance at %{ruby_archdir} and 
%{ruby_rubylibdir} macros occurrence in ruby-*.spec - whereas others into 
%{ruby_sitelibdir} and %{ruby_sitearchdir} ? Here are values from ruby Config 
for better comprehension:

$ ruby -r rbconfig -e 'include Config; CONFIG.each_pair {|x,y| puts "#{x} = 
#{y}";}' | grep "dir = /usr/lib/ruby" | sort
archdir = /usr/lib/ruby/1.8/i686-linux
rubylibdir = /usr/lib/ruby/1.8
sitearchdir = /usr/lib/ruby/site_ruby/1.8/i686-linux
sitedir = /usr/lib/ruby/site_ruby
sitelibdir = /usr/lib/ruby/site_ruby/1.8
topdir = /usr/lib/ruby/1.8/i686-linux

I've checked ruby-Ncurses.spec and compared it to Debian and FreeBSD packages. 
libncurses-ruby1.8 from Debian[1] uses "ruby system directories" whereas 
FreeBSD port "site directories" [2], so I've gotten stuck.

[1] 
http://packages.debian.org/cgi-bin/search_contents.pl?searchmode=filelist&word=libncurses-ruby1.8&version=stable&arch=i386
[2] 
http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/ports/devel/ruby-ncurses/pkg-plist?rev=1.7

-- 
Tomasz Wittner