> 0) We try to provide as much support as possible for all ruby interpreters
> (well, at least 1.8 and 1.9.1, but maybe also jruby). However, we decide
> on a default version (1.8 currently) that all libraries must support.
We'll release Ruby 1.9.2 in this summer.
So where 1.9.2 will install, /usr/lib/ruby/1.9.1 or /usr/lib/ruby/1.9.2?
Note that 1.9.2 intends to have ABI compatibility to 1.9.1.
> 2) Instead of installing to /usr/lib/ruby/1.{8,9.1}, we install to:
> /usr/lib/ruby/vendor_ruby/ <= libraries that support all versions
> of the interpreter
> /usr/lib/ruby/vendor_ruby/1.8 <= libraries that only support 1.8
> /usr/lib/ruby/vendor_ruby/1.9.1 <= libraries that only support 1.9.1
> That allows to make a better difference between the stdlib and the
> third-party libraries.
What will you do about a gem supports 1.8 and 1.9.1 but not 1.9.2.
> 5) Regarding test suites, we should really try to execute them during the
> build (for every ruby implementation), as this will allow to detect
> regressions.
MRI's test-all has some stress test.
--
NARUSE, Yui <nar...@airemix.jp>
--
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/4bd02780.8060...@airemix.jp
