On Mon, Jan 06, 2014 at 01:22:15PM -0800, Russ Allbery wrote: > I maintain a package (remctl) that builds, among other things, a Ruby > extension. I noticed that it showed up as affected by the upcoming > ruby1.8-removal transition, and I think this may be the relevant bug. (At > least, it's the only open bug that looks relevant.) > > 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). -- Antonio Terceiro <terce...@debian.org>
signature.asc
Description: Digital signature
