[chef] Re: Re: Ruby, Chef, Omnibus and you!

[Alex Howells < >]

On 30 December 2011 22:23, Joshua Timberman 
<
 >
 wrote:
>
> Ah, of course. The package compiled against the version of Ruby available 
> in the distribution, since is a C extension, so in order to work with the 
> Ruby in the Chef Full Stack installation, it needs to be recompiled with 
> that version of Ruby (1.9.2p180). That's fine in many environments - to 
> build C extension RubyGems on systems when installing the gem, but not in 
> environments where C compiler and build toolchains are prohibited from 
> servers by security policy.
>

If Omnibus is "The Future" then I'm guessing the Ruby which you ship
inside it is going to have a *lot* of stuff bolted on.

Is that something you've thought about and are okay with?

I'm generally a little concerned that Omnibus could be very divisive.
Those who can use it and benefit, because their needs are simple, and
those who are excluded because they want to use a technology (SELinux)
which is not included and supported.

Whilst I appreciate you will never cater to all needs, and there is a
core of 'power user' out there who will always do their own thing, the
recommended route for deploying chef-client (which seems to be heading
in an Omnibus direction) needs to cater for the masses, and that
*does* mean things like SELinux (amongst other things) will become
increasingly important to support properly.

Cheers,
 -Alex