On Thu, Feb 06, 2014 at 04:20:20PM +0100, Christian Hofstaedtler wrote: > Control: tags -1 + confirmed > Control: affects -1 + src:ruby-defaults > > Hi, > > Francesco Poli wrote: > > Is there a working strategy for setting the default system-wide Ruby > > interpreter in a clean and practical way? > > No, this is no longer a supported scenario. > > > Should ruby-switch be adapted to the new strategy or should it be > > removed from Debian sid? > > Indeed, ruby-switch in it's current form does not work; I'm not sure > if there were plans for a user-wide switching strategy in > ruby-switch, or if the recommendation will be rbenv.
`rbenv alternatives` is also currently broken, but is fixable. To be honest I'm not sure yet about what to do with ruby-switch. Since we don't have plans to keep multiple interpreters in the archive for long periods of time, ruby-switch is now a little pointless. We can support people switching to the newest interpreter before it becomes the default by having an updated ruby-defaults in experimental (as it is the case now). > In any case, ruby-defaults should have had a Conflicts: ruby-switch > (<< 0.1.0). I think maybe Breaks is better, but yes. -- Antonio Terceiro <terce...@debian.org>
signature.asc
Description: Digital signature
