[chef] Re: Re: Re: Re: Re: Providing specific version numbers of packages to install with yum...

[Joshua Timberman < >]

There isn't a semantic to do version constraints on package resources

However, you could assign it through a node attribute. Then when you have 
vetted a new version for your infrastructure you can modify the version. I 
suggest setting a base version in the cookbook's attributes file as so:

default['erlang']['version'] = "R14B-03.3.el5"

Then you can modify through a role:

name "erlang-service"
default_attributes(
  'erlang' => {
    'version' => "R14B-03.4.el5"
  }
)

Replace "erlang-service" with the appropriate name of the service that uses 
Erlang, e.g., rabbitmq.


On Oct 24, 2011, at 8:55, Brad Knowles 
<
 >
 wrote:

> On Oct 21, 2011, at 10:25 PM, AJ Christensen wrote:
> 
>> yum_package "someshit" do
>> version "1.2.3-whatever"
>> end
> 
> I can confirm that this form works:
> 
>  yum_package "erlang" do
>    version "R14B-03.3.el5"
>  end
> 
> However, that ties us to a specific version of Erlang, which I'd rather not 
> do as a part of the recipe.  I'm sure I could over-ride this from a role, 
> but is there a more elegant way to specify that we need something greater 
> than version R12B, but without tying us to a specific version & release?
> 
> -- 
> Brad Knowles 
> <
 >
> SAGE Level IV, Chef Level 0.0.1
>