Just a heads up that there is a discussion taking place on the
puppet-dev list about packaging changes for puppet 4.x on platforms that
don't provide ruby > 1.8.7.
PL is planning to vendor all dependencies into a single "all in one"
package. I've suggested a puppet SCL for el6.x but thus far I'm a lone
voice. If you have an opinion on this topic, now would be a good time
to express it.
Cheers,
-Josh
···
--
While using an SCL would be nice for consistency, I don't think it'd
help us much as there are other platforms that don't have SCLs
implemented. I think either way we'd need to handle the changes.
Probably best to try moving to a smart proxy model that doesn't involve
loading Puppet libraries directly, or moving it to a shim within the AIO
environment.
···
On 19/11/14 18:13, Joshua Hoblitt wrote:
> Just a heads up that there is a discussion taking place on the
> puppet-dev list about packaging changes for puppet 4.x on platforms that
> don't provide ruby > 1.8.7.
>
> PL is planning to vendor all dependencies into a single "all in one"
> package. I've suggested a puppet SCL for el6.x but thus far I'm a lone
> voice. If you have an opinion on this topic, now would be a good time
> to express it.
–
Dominic Cleal
Red Hat Engineering
