* Miguel Landaeta [16 22:46]:
> Resuming the discussion about this bug, I believe the best solution we
> can come up right now is to drop the Provides for ruby-interpreter in
> jruby, given how late we are on the release cycle already.
>
> However, I'd like to revisit this issue during "buste
Hi,
Resuming the discussion about this bug, I believe the best solution we
can come up right now is to drop the Provides for ruby-interpreter in
jruby, given how late we are on the release cycle already.
However, I'd like to revisit this issue during "buster" development
cycle.
jruby provides hi
* Helmut Grohne [161004 06:59]:
> I think the implications of having jruby drop ruby-interpreter deserve
> more thought from the ruby team.
>
> It appears to me that jruby would just work with a fair amount of ruby
> modules[1]. Yet, after dropping that provides, trying to install e.g.
> jruby an
On Mon, Oct 03, 2016 at 04:46:11PM -0700, tony mancill wrote:
> I agree with Helmut's suggestion that jruby should drop the Provides.
> Even if there are contexts in which jruby could act as a ruby
> interpreter, I don't think we should encourage our users to use it
> when we have ruby available.
4 matches
Mail list logo
