- From: Bryan McLellan <
- Subject: [chef] Re: Re: Re: Re: Re: Chef on Ruby 1.8.6
- Date: Fri, 25 May 2012 17:50:11 -0400
On Fri, May 25, 2012 at 5:10 PM, Jamie Winsor
> Hey Bryan, why do we care about old versions of Ruby if we've got the
> omnibus installer which allows us to dictate which Ruby Chef is run with?
> Are we trying to preserve the right for users to still run Chef with system
In keeping with the philosophy that Chef shouldn't force you to model
your infrastructure the same way we do, we don't want to force the
user to install Chef the way we think is best.
For various reasons, perhaps just corporate requirement or personal
preference, not everyone is going to use Omnibus. Some users want to
use a single package manager on their systems to track all software
that is installed. This is one reason Omnibus wraps itself in a deb or
rpm when possible. Other users prefer to use upstream packages
wherever possible. For disk space, security, or copyright licensing
reasons, a user may not want an additional stack in /opt that they do
not manage. Maybe you have a functional ruby stack somewhere and want
Chef but there isn't an Omnibus installer for their architecture or
At Opscode, we provide tools and you can build your own [bike] shed. :)
Archive powered by MHonArc 2.6.16.