> So, the bigger problem here would seem to be one of long-term support.
> In other words, trying to find common ground between release cycles.
I really think the issue of versions and support cycles is not that big
a deal. There are lots of places that one could stick updated packages.
The big problem IMO that needs to be solved to package Cassandra is the
same as for a lot of other Java software: the fact that there are so
many dependencies, and Cassandra just ships them as binary jar files as
part of the main package. Any sane distro packaging is going to want
separate packages for all the independently developed dependencies --
for example if a security issue is found, a distro wants to patch it
once, not have to hunt down which of a 100 Java packages shipped their
own private jar with the bug.
- R.
--
Roland Dreier <rol...@digitalvampire.org> GPG Key: 4096R/B4F83169
Fingerprint: 3779 F472 BB84 DFE1 A650 C304 DDC7 ECFB B4F8 3169
Sending >500KB attachments is forbidden by the Geneva Convention.
Your country may be at risk if you fail to comply.
