[chef] Re: Re: Re: Re: Re: Re: Re: Re: chef-client gem install --pre doesn't find second level dependencies?

[KC Braunschweig < >]

> We do provide deb packages in our apt repository for those who don't
> want to install from source. [1]
>
> However, Chef 0.10 isn't released yet; and we're still at the release
> candidate stage. The expectation for beta and RC releases is that
> users are not going to install them directly into a production
> environment. It is the period where we all test the software ourselves
> and try to find any major bugs in the new release. If you don't want
> the hassle of building a development environment, I'd advise sticking
> with the official releases. Shortly after the official final release
> of 0.10.0, we'll be putting up apt packages for 0.10, as described
> recently on the Opscode blog [2]. I'm actually working on them right
> now.
>
> In either case, it isn't that you need a newer version of Rubygems for
> Chef 0.10, it is that older versions of Rubygems presumably aren't as
> good at resolving dependencies when using "--pre" to fetch
> prereleases.

Totally understood regarding chef 0.10 and all beta/RC releases for
that matter.

My question was meant more generally as the requirements on that page
(specifically recommending source installed rubygems on ubuntu and
debian) are general chef requirements, not chef 0.10 specific. While I
wouldn't have hit this particular issue had I been installing a non
prerelease version, assumably I would have hit some issue or other or
else you wouldn't be recommending installing rubygems from source for
all versions.

KC