Lucas Nussbaum dijo [Wed, Jan 19, 2011 at 08:01:57PM +0100]: > > Run the test suite four times per package, once with each interpreter? > > Well, of course it gives better coverage... But some test suites are > > quite long to run. And if we reach a stage where the different > > interpreters are compatible enough, it might be pointless. > > > > Also, it bloats our build-dependencies. If I have to install > > traditional Ruby, Java (to get jruby) and Mono (to get IronRuby), and > > whatever it takes to run Rubinius... Well, setups will be huge. > > Who cares? I don't think that we should trade off quality for build > time.
Ok... I have nothing to counter that with :) > > Do you think Ruby has reached a stability point where it can be > > handled through alternatives? i.e. where a user can change > > /usr/bin/ruby to point from ruby to jruby and expect random programs > > not to break? > > No. But we could do like Java: support the default version, do our best > with alternative implementations, but provide a way for users to switch > implementations if they want to, since it makes it easier for them to > test with several implementations. > > It's a very common request, and one that is fullfilled with RVM, which > proves that there's interest for it. Oh, I didn't know it was a popular request. In that case, then, yes - As long as it's still legal to ship a package that works only with one/some of the implementations (of course, with dependencies reflecting it), I'm cool with it. -- To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110119190419.gh4...@gwolf.org
