F20: Puppet depchain pulls in Java

Vít Ondruch vondruch at redhat.com
Mon Jan 20 09:52:04 UTC 2014

Dne 18.1.2014 07:40, Michael Stahnke napsal(a):
> On Fri, Jan 17, 2014 at 6:53 PM, Rahul Sundaram <metherid at gmail.com> wrote:
>> Hi
>> On Fri, Jan 17, 2014 at 9:43 PM, Mo Morsi  wrote:
>>> Yes as others have mentioned puppet requires ruby(release) which is
>>> satisfied by both ruby-mri and jruby
> So should it just require ruby-mri?
> The divergence from the way upstreams handle ruby here is quite
> difficult to work with. I find ruby-pick 

ruby-pick has hardly anything to do with upstream similarly to RVM.

> and bundler patching to be
> less fun/friendly than having what I'd expect form upstream.

This is going to be resolved with RubyGems 2.2 I hope.

>  I'm not
> in love with the way upstream handles/does things, but I don't really
> understand what happened to the 'upstream first' mantra. Here we
> (Fedora) just made up their own rules and moved forward.
>> ... which is fine.  However yum install puppet should be pulling in only
>> one.  Not both.  I would say almost everybody would expect that to be
>> ruby-mri
> I would say exactly everybody, since on jruby there are issues.

If only RPM could give us way how to give a hint that MRI is preferred,
if nothing satisfies ruby(runtime_executable) ....


More information about the devel mailing list