Re: Whither site_ruby?

Shugo Maeda <[email protected]> writes:
> Dan Cross wrote:
> >>``make site-install'' installs libraries into /sw/lib/ruby/1.8/1.8 on my
> >>machine.
> > 
> > 
> > Even the corrected path, /sw/lib/ruby/1.8, is not where I want them to
> > go.  I want them to go into ${prefix}/lib/ruby/site_ruby/1.8, which I
> > then merge into /sw/lib/ruby/site_ruby/1.8 with stow (or epkg, or a similar
> > tool).  In this case, ${prefix} is not ``/sw'', but something like
> > ``/contrib/packages/mod_ruby/1.2.4.''
> 
> --with-search-path option of configure of ruby may help you.
> 
>   $ ./configure --with-search-path=/sw/lib/ruby/site_ruby/1.8
> 
> --with-search-path adds /sw/lib/ruby/site_ruby/1.8 to $:, but do not
> change $sitedir.

I tried that, too, but then various C extensions wouldn't build
because they couldn't find the Ruby header files (I think perhaps
the Ruby postgres extension).  I didn't try and track it down too
far beyond that; instead it just seemed like a better idea to try
and get everything into $sitedir.

> > But I am curious why Ruby doesn't install
> > into site_ruby by default;
> 
> The recent ruby installs extension libraries into sitedir by default.
> mod_ruby installs them into rubylibdir by the historical reason, but
> It may be the time to change it.

Okay.  That'd be great, as it'd make life for those of us maintaining
things in slightly unusual ways much easier.  :-)

Thanks for all your help on this, Shugo!  It is very much appreciated,
and may I also say that mod_ruby is wonderful and also very much
appreciated!

	- Dan C.