Chef on Ruby 1.8.6


#1

Does anyone still run Chef on Ruby 1.8.6?


Bryan McLellan | opscode | technical program manager, open source
© 206.607.7108 | (t) @btmspox | (b) http://blog.loftninjas.org

http://tickets.opscode.com/browse/CHEF-2329


#2

Ruby 1.8.6 has been reached end of life on Engine Yard, and I know no
distro with Ruby 1.8.6 for now.

2012/5/25 Bryan McLellan btm@opscode.com

Does anyone still run Chef on Ruby 1.8.6?


Bryan McLellan | opscode | technical program manager, open source
© 206.607.7108 | (t) @btmspox | (b) http://blog.loftninjas.org

http://tickets.opscode.com/browse/CHEF-2329


#3

On Fri, May 25, 2012 at 12:57 PM, Akzhan Abdulin
akzhan.abdulin@gmail.com wrote:

Ruby 1.8.6 has been reached end of life on Engine Yard, and I know no distro
with Ruby 1.8.6 for now.

CentOS 5.x is still all Ruby 1.8.5. Since lots of enterprises are
still back in that world this means a lot of possibilities for where
they’re currently getting their Ruby.

Bryan


#4

Current CentOS is on 6.x way.

But you’re right.

2012/5/25 Bryan McLellan btm@loftninjas.org

On Fri, May 25, 2012 at 12:57 PM, Akzhan Abdulin
akzhan.abdulin@gmail.com wrote:

Ruby 1.8.6 has been reached end of life on Engine Yard, and I know no
distro
with Ruby 1.8.6 for now.

CentOS 5.x is still all Ruby 1.8.5. Since lots of enterprises are
still back in that world this means a lot of possibilities for where
they’re currently getting their Ruby.

Bryan


#5

On 05/25/2012 10:28 AM, Bryan McLellan wrote:

On Fri, May 25, 2012 at 12:57 PM, Akzhan Abdulin
akzhan.abdulin@gmail.com wrote:

Ruby 1.8.6 has been reached end of life on Engine Yard, and I know no distro
with Ruby 1.8.6 for now.

CentOS 5.x is still all Ruby 1.8.5. Since lots of enterprises are
still back in that world this means a lot of possibilities for where
they’re currently getting their Ruby.

This is why omnibus is so awesome. :slight_smile:


Phil Dibowitz phil@ipom.com
Open Source software and tech docs Insanity Palace of Metallica
http://www.phildev.net/ http://www.ipom.com/

“Be who you are and say what you feel, because those who mind don’t matter
and those who matter don’t mind.”

  • Dr. Seuss

#6

I second this.

Hey Bryan, why do we care about old versions of Ruby if we’ve got the omnibus installer which allows us to dictate which Ruby Chef is run with? Are we trying to preserve the right for users to still run Chef with system Ruby?

Jamie Winsor
@resetexistence

On May 25, 2012, at 1:55 PM, Phil Dibowitz phil@ipom.com wrote:

On 05/25/2012 10:28 AM, Bryan McLellan wrote:

On Fri, May 25, 2012 at 12:57 PM, Akzhan Abdulin
akzhan.abdulin@gmail.com wrote:

Ruby 1.8.6 has been reached end of life on Engine Yard, and I know no distro
with Ruby 1.8.6 for now.

CentOS 5.x is still all Ruby 1.8.5. Since lots of enterprises are
still back in that world this means a lot of possibilities for where
they’re currently getting their Ruby.

This is why omnibus is so awesome. :slight_smile:


Phil Dibowitz phil@ipom.com
Open Source software and tech docs Insanity Palace of Metallica
http://www.phildev.net/ http://www.ipom.com/

“Be who you are and say what you feel, because those who mind don’t matter
and those who matter don’t mind.”

  • Dr. Seuss

#7

On Fri, May 25, 2012 at 5:10 PM, Jamie Winsor jamie@vialstudios.com wrote:

Hey Bryan, why do we care about old versions of Ruby if we’ve got the omnibus installer which allows us to dictate which Ruby Chef is run with? Are we trying to preserve the right for users to still run Chef with system Ruby?

In keeping with the philosophy that Chef shouldn’t force you to model
your infrastructure the same way we do, we don’t want to force the
user to install Chef the way we think is best.

For various reasons, perhaps just corporate requirement or personal
preference, not everyone is going to use Omnibus. Some users want to
use a single package manager on their systems to track all software
that is installed. This is one reason Omnibus wraps itself in a deb or
rpm when possible. Other users prefer to use upstream packages
wherever possible. For disk space, security, or copyright licensing
reasons, a user may not want an additional stack in /opt that they do
not manage. Maybe you have a functional ruby stack somewhere and want
Chef but there isn’t an Omnibus installer for their architecture or
platform yet.

At Opscode, we provide tools and you can build your own [bike] shed. :slight_smile:

Bryan