The problem is that there are differences between 1.9.1 and 1.9.2 that will
break existing 1.9.1 code. I really think you need to bump the package name to
ruby1.9.2.
Hello Lucas,
Thank you for that answer. I can now see there is a logical reason for
the numbering. May I suggest adding a line to the package description
stating simply "This is the Ruby version compatible with Ruby 1.9.1"
or something similar to clarify this for posterity. It would be very
useful
On 26/10/10 at 22:05 -0500, Tom wrote:
> Package: ruby1.9.1
> Version: 1.9.2.0-1
>
> So Ruby 1.9.2 is now in the Debian package ruby1.9.1. In the mean time
> there is a Debian package named ruby1.9 that seems to be abandoned.
> For the Ruby 1.8 branch there is a package called ruby1.8 (aka ruby)
>
Package: ruby1.9.1
Version: 1.9.2.0-1
So Ruby 1.9.2 is now in the Debian package ruby1.9.1. In the mean time
there is a Debian package named ruby1.9 that seems to be abandoned.
For the Ruby 1.8 branch there is a package called ruby1.8 (aka ruby)
which always has the latest 1.8.x version of Ruby.
4 matches
Mail list logo
