[chef-dev] Re: Ohai Ruby plugin: system ruby vs. running ruby?

[Daniel DeLeo < >]

On Wednesday, August 31, 2011 at 12:50 PM, Brad Knowles wrote:
> On Aug 31, 2011, at 2:32 PM, Daniel DeLeo wrote:
> 
> > There's a few things we could do about this:
> > 1. Always use the Ruby that you're using for ohai/chef-client. If we do 
> > this, we could avoid shelling out entirely and the ruby plugin would run 
> > faster.
> 
> For those of us who have used the Omnibus installer, there is an embedded 
> version of Ruby that is included. The path to that embedded version should 
> be included in any Chef or Chef-related code that runs on the system, and 
> that process should be instantiated at install/compile time -- no need to 
> search around for which version of ruby to run, you brought your own 
> version of ruby with you, and you know that's the one you always want to 
> use.
> 
> Moreover, the user path should not have to be modified to include the 
> directory for /opt/opscode/embedded/bin/ruby, nor should there be a symlink 
> to this executable created in /usr/bin, /usr/local/bin, or any other 
> standard (or semi-standard) location.
> 
> This entire problem can be fixed in stone at the time of install/compile, 
> and if you need to upgrade (or downgrade) the embedded version of ruby, you 
> should be able to do that pretty much completely independently of 
> everything else on the system. That's why it's called "embedded".
> 
> 
> We had some discussions on this topic in #chef. I would encourage you to go 
> check the logs.
> 
So, if your ohai attributes for languages/ruby are empty, what breaks?


-- 
Dan DeLeo 
> -- 
> Brad Knowles 
> <
 
>  
> (mailto:
 )>