On 06/26/2011 06:08 PM, Ken Bloom wrote:
Package: scala Version: 2.8.1.dfsg-1 Severity: normal
Different versions of Scala are binary-incompatible with each other,
when the minor version number changes. (So Scala 2.8.0 is compatible
with Scala 2.8.1, and Scala 2.9.0 is compatible with Scala 2.9.0.1,
but Scala 2.9.x is incompatible with Scala 2.8.x).
Please package scala with a version number in the package name, so
that different versions of scala can be installed simultaneously, and
to avoid dependency conflicts (like how python and ruby have version
numbers in their package names). Please also add a version number to
the name of the jar file (i.e. scala-2.8.jar, scala-2.9.jar)
That could be done *iff* we intend to support multiple versions of Scala
at the time. But, I'm not sure that it's the best thing to do right now.
Scala is moving fast. Old versions are not supported upstream. So, we
cannot keep them long time in the archive after a new release comes out.
You mentioned Python and Ruby but those have the concept of a "long term
stable release". So, they can support multiple versions of the same
interpreter/compiler at the same time *and* have upstream's support for
that. AFAIK, Scala doesn't have any equivalent for that.
But, sure, we can make those packages co-installable, and so on… but, it
seems overkill given the current state of affairs. If Scala gains a
concept of long term stable releases, then we will re-consider our policy.
Regards,
--
Mehdi Dogguy مهدي الدڤي
http://dogguy.org/
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
