On Mon, Feb 24, 2003 at 03:47:44AM +0900, Edward Wilson wrote:
> > That said, there are other issues with the RPM, such as the packager's
> > decision to have libraries go into /usr/lib/site_ruby, rather than
> > /usr/lib/ruby/site_ruby, which would make it analogous with the Perl and
> > Python RPMs.
> 
> Everyone please bear with me; I'm still getting used to the Ruby file
> layout.

[snip] 
> The C API as well as the ease of finding and building applications
> with the .c, .h, .so, and lib (on windows) files is a big deal!  Not
> finding all of these files where one expects them is annoying.  These
> are those small details that make it easy to put off using Ruby for
> another year.  When I install Ruby or any tool on my system, I expect
> all of the `include' and `library' files to be neatly organized and
> easy to find.  Once I run `make install' I don't want to have to
> download more files or manually move files aroundͪ want everything to
> be in its place ready to go.  You guys are much smarter than I am, why
> is the Ruby file structure so obtuse?

some things to consider:
 * you don't want to know where extensions' .so files are. Period. You're
   not linking against them, they're loaded when you do 'require' or 'load' 
   inside Ruby, and it does know where they are.
 * the only .so (dll) you might want to link against is libruby.so,
   available in /usr/lib/ or /usr/local/lib depending on your packaging
 * as for .c files, why would you need them? Everything you need to link
  against is in libruby.so or libruby.a, so, why do you need the
  interpreter's sources?
 * extensions using 'extconf.rb' will use platform-tailored makefiles
  and know where everything is 

Summing up, unless you have strange needs, you'll find "everything to be
in its place ready to go."

-- 
 _           _                             
| |__   __ _| |_ ___ _ __ ___   __ _ _ __  
| '_ \ / _` | __/ __| '_ ` _ \ / _` | '_ \ 
| |_) | (_| | |_\__ \ | | | | | (_| | | | |
|_.__/ \__,_|\__|___/_| |_| |_|\__,_|_| |_|
	Running Debian GNU/Linux Sid (unstable)
batsman dot geo at yahoo dot com

I've no idea when Linus is going to release 2.0.24, but if he takes
too long Im going to release a 2.0.24unoff and he can sound off all
he likes.
	-- Alan Cox