On Sun, 27 Jul 2014 01:57:22 +0200 Christian Hofstaedtler wrote: > Re: ruby-debian no longer supporting ruby2.0, but apt-listbugs runs > with 2.0 during a partial upgrade > > Given your description it would appear that all ruby packages would > need to gain explicit rubyX.Y dependencies (similar to how this > works for the Python packages). > > As an alternative, ruby-debian (and other known packages) may choose > to Break older rubyX.Y versions. I would think that the second alternative is more practical than the first: it should require changes in a significantly smaller set of packages, shouldn't it? Moreover it looks conceptually more correct: after all, it's ruby-debian and the other compiled Ruby libraries that no longer support ruby2.0! apt-listbugs and many other pure Ruby programs or libraries are instead perfectly able to be interpreted by ruby2.0, as long as the compiled Ruby libraries they depend on still support ruby2.0... Or am I completely off-track? -- http://www.inventati.org/frx/ fsck is a four letter word... ..................................................... Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE
Attachment:
pgpgZ11wnOSKr.pgp
Description: PGP signature