Bug#722980: Status of ruby1.8 removal transition?
Antonio Terceiro <terceiro@debian.org> writes:
> On Mon, Jan 06, 2014 at 01:22:15PM -0800, Russ Allbery wrote:
>> On my next package upload, should I just drop Ruby 1.8? I can easily
>> do that, but I wasn't sure if we were at the point where that was now
>> desirable, or if the upgrade path for Ruby 1.8 users had been worked
>> out and had any implications for how I should handle matters in my
>> package. (Breaks or whatnot, etc.)
>> For now, I'm continuing to build 1.8 and 1.9.1 modules, but I can
>> quickly change that as soon as I know what to do.
> Our goal is to remove ruby1.8 and switch to ruby2.0 as the default,
> ASAP, so it would be nice if you started building extensions for 1.9.1
> and 2.0 (only).
I guess I should ask this more explicitly: what's the plan for handling
upgrades from wheezy? Suppose a user has ruby1.8 installed and is using
it for various things along with packaged Debian modules, say ruby-remctl
(to pick a random example). They then upgrade their system to wheezy.
Ruby 1.8 doesn't upgrade, of course, but neither does it disappear from
the system... but ruby-remctl does upgrade, and then the Ruby modules for
1.8 disappear out from under them without much warning.
Don't we need to handle this in some way?
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: