omnibus bundles everything above glibc in a single self contained package,
hence it will work out of the box. system’s ruby on the other hand might
need ssl, readline etc native libraries. But this is certainly possible, we
all used to do this pre-omnibus.
another important aspect will be how chef_gem and other resources work.
With omnibus you can build your own ops tooling without polluting system’s
ruby gem set.
on the negative side, you will be tied with an older version of ruby
(currently 2.1, omnibus ships with 1.9),
On Wed, Feb 12, 2014 at 11:09 PM, Peeyush Gupta firstname.lastname@example.org wrote:
Thanks Daniel, that works. Thought I would like to know is there any
difference between installing chef through omnibus and gem?
On Thursday, 13 February 2014 12:10 PM, Daniel Condomitti <
Use the enterprise linux 6 packages. It works with RHEL, CentOS and
Fedora. If you use the omnibus installer (the curl | bash command) it
should figure everything out automatically.
On Wednesday, February 12, 2014 at 10:38 PM, Peeyush Gupta wrote:
So, I am trying to learn about chef. As I wanted to install it, so I went
to www.opscode.com/chef/install. Now, I am using Fedora and I don’t find
any package for Fedora there. I mean there is Enterprise Linux but no
Fedora. So, I installed chef using rubygem (i.e gem install chef). How is
that different from downloading the package from opscode? Are they the same
thing? Plus if I had to download from opscode which enterprise linux should
I go for,5 or 6?
P.S: I am using Fedora 18.