I'm relying on `make install` being able to install libs to an
arbitrary directory (which is then slurped by the packaging system at
powerset). The site_ruby method is still useful for groups packaging
multiple language libraries.

I'd be happy to make this a configure time option, and default to gems.

On Tue, Nov 11, 2008 at 12:11 PM, Bryan Duxbury <[EMAIL PROTECTED]> wrote:
> We already have code in the Ruby libraries for packaging as a gem. Gems are
> clearly the preferred method of managing libraries in the Ruby world. So why
> does "make install" in the ruby lib put the bare library code in site_ruby?
> This strange arrangement makes it really, really easy to get yourself
> confused when developing on the ruby libs, since the site_ruby install takes
> precedence over any gem install.
>
> Is anyone relying on this site_ruby installation behavior, or is it
> something we can just get rid of?
>
> -Bryan
>



-- 
Kevin Clark
http://glu.ttono.us

Reply via email to