> 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."

I don't have any use for standalone Ruby.  It's when I can extend and
or embed Ruby that I have infinite use for Ruby.  So for me, the thing
that matters most is where the C files and libs are; and that they are
ALL there.

--
ed