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

[Adam Jacob < >]

On Wed, Apr 20, 2011 at 4:35 PM, KC Braunschweig
<
 >
 wrote:
> 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.

The deal here is that Debian and Ubuntu make a series of policy
decisions about how to structure the libraries they ship with the
operating system. That's cool - it's the reason distributions exist,
after all. Next to that is the evolving ruby ecosystem - ruby itself
moves forward, bugs are fixed, and rubygems continues to become the
most common way to build and deploy ruby applications. Occasionally
those policy decisions conflict - in this case, Debian and Ubuntu both
ship with old versions of rubygems that also have tweaked library
paths from the norm (specifically, there is an issue with where
binaries are placed.)

So we make choices - in this case, we advise people to no longer run
the debian/ubuntu version of rubygems, and we work to get a change in
policy. That takes time, and so in the mean-time we guide people down
the path we know will result in a system that behaves as you would
expect.

The future solution to this problem will be full-stack installers
delivered both as stand-alone installable binaries and native
packages, but with the entire dependency chain included.  That this is
the right solution is starting to be pretty widely embraced - you can
see the evidence in several past package maintainers for chef moving
to a model exactly like this.

Best,
Adam

-- 
Opscode, Inc.
Adam Jacob, Chief Product Officer
T: (206) 619-7151 E: