- From: AJ Christensen <
>
- To:
- Subject: [chef] Re: Re: Re: Re: Re: Gem install on Ubuntu 12
- Date: Mon, 23 Jul 2012 20:22:43 +1200
I do not believe that 'chef_gem' is being phased out. Opscode could
confirm -- Perhaps the documentation author (one of my team mates)
meant that the 'chef_gem' Heavy Water cookbook would no longer be
required post 10.12.0 or so.
In some states, you may have deployed Chef via gem to an embedded
system interpreter. In this case, the chef_gem cookbook,
omnibus_updater and gem_installer cookbooks will allow you to
transition to newer cookbooks that use the 'chef_gem' method of
installing a gem to the embedded Opscode Chef interpreter instead of
the system interpreter (which generally requires another Ruby
installation).
In some states, you may have deployed a system and an updated Chef
'full stack' omnibus installation may have been released, again, our
cookbooks will help.
In alternate states, you may have deployed multiple rubies to a single
system and require the capability to install gems to any-which of
them; again, our cookbooks will allow you to achieve this.
I can't possibly know which of these states your infrastructure is in;
I leave the adventure up to you :)
I neglected to mention one, possibly helpful in the event you require
a system Ruby installation [0]
--AJ
[0]
http://community.opscode.com/cookbooks/ruby_installer
On 23 July 2012 20:05, Steve Bennett
<
>
wrote:
>
On 23 July 2012 17:52, AJ Christensen
>
<
>
>
wrote:
>
>
>
> I fear you've seen a case where an out of date cookbook in an old
>
> version of a snapshot repository hasn't been updated to use 'chef_gem'
>
> resource to install gem to the Opscode Chef embedded Ruby
>
> installation.
>
>
>
> In the culprit recipe, if you change gem_package "pg" etc to chef_gem
>
> "pg", that should remedy it!
>
>
>
Should gem_package be deprecated, then?
>
>
>
>
>
>
> Most of the Opscode cookbooks on the community site have been updated
>
> to support the new Omnibus based installations.
>
>
>
> At Heavy Water, we developed the 'chef_gem' cookbook to allow "Forward
>
> Compatibility" for ~> 0.10.0 to use the 'chef_gem' resource.
>
>
>
Whee, confusing. From http://community.opscode.com/cookbooks/chef_gem:
>
>
--
>
This cookbook is a transition cookbook aimed at helping move from the
>
pre-chef_gem era to the post chef_gem era. The chef_gem resource was
>
introducde in Chef 0.10.9, providing an easy mechanism for installing and
>
using gems required by Chef internally. When used within an omnibus
>
installation, chef_gems are installed within the embedded Ruby.
>
--
>
>
From the perspective of someone who just wants to get a cookbook to work,
>
this is a lot of confusing detail about the internals of Chef, gems, etc.
>
What is the "post-Chef_gem era"? Is chef_gem being phased out?
>
>
Steve
>
Archive powered by MHonArc 2.6.16.