| Summary: | app-admin/puppet-3.6.2 - add ruby 2.1 support | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Ivan Bagaev <gmiramir> |
| Component: | Current packages | Assignee: | Matthew Thode ( prometheanfire ) <prometheanfire> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | gmiramir, jowr.pi, lists, ruby, sysadmin |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Ivan Bagaev
2014-06-23 17:05:07 UTC
Could we get Ruby 2.1 support added? puppet-4.0.0 has ruby21 support. Is there a specific reason that it should be backported to older versions? Because I want to stabilize it faster then ruby21 will be stabilized. I personally will not be using Puppet 4.0 for a little while because even though a lot of the feature sets 4.0 is using are in 3.7.x, it is going to take awhile for me to be satisfied that it is safe to upgrade a production environment to it. On the other hand, we already know 3.7.x has stable Ruby 2.1 support as per the official puppetlabs testing matrix and that upgrading the puppet ebuild to build against it is as easy as making sure the puppet ebuild and the other core ruby-related tools (hiera and such) have the ruby21 ruby target. The reasoning for this is because Ruby 2.1 is faster than 2.0, which matters for me because I have a master that builds absolutely massive catalogs for certain clients and its' starting to get out of hand. Another 5% speed will make life easier. Plus let's be realistic, Puppet 2.7 sat in portage for a year past its' expiration date until I pushed to have it removed :3 OTOH if the goal is to focus on 4.x with the explicit argument that 2.0 is good enough, then that's fine. It just needs to be clear. (In reply to Matthew Thode ( prometheanfire ) from comment #4) > Because I want to stabilize it faster then ruby21 will be stabilized. we can add an -r1 version for e.g. 3.7.4 with ruby21 support. I'd be happy to add that (and do the same for future puppet 3.x versions, if any. fixed in 3.7.4-r1 |
