Hola Lucas Nussbaum! > Could you share what is your use case for ruby1.8?
I have internal packages that depend on ruby1.8, that have #!/usr/bin/ruby1.8 in the interpreter line, so they would work regardless of the alternatives system, but they need an installed ruby1.8 interpreter. Yes, one can argue that I should migrate those, but that takes time, and I don't think what is being done here is the right way to go. > What is different in that specific case is that at some point we > provided support for multiple versions, and are now removing that. > But nothing prevents users from using the version of ruby(1.8) in wheezy > on their jessie system. that means they have to keep other packages at > their wheezy version, but that's what would happen too if you wanted to > run the GTK version from wheezy. But the point is that you can't really keep ruby1.8 from wheezy because ruby now conflicts with ruby1.8. So, in order to keep ruby1.8, you need to also keep ruby, ruby1.9 and any versioned dependencies. This is the point that I find unacceptable. It's perfectly fine to tell users that in order to use ruby1.8 they need to use wheezy's package. But what's happening here is that in order to use ruby1.8 one needs to keep the whole ruby stack from wheezy. I would really appreciate if this was reconsidered. -- Regards, Marga -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
