[
https://issues.apache.org/jira/browse/CASSANDRA-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13146403#comment-13146403
]
paul cannon commented on CASSANDRA-3458:
----------------------------------------
So this is going to result in Cassandra depending on python-cql, which in turn
depends on python-thrift, neither of which will be found in any official
Debian/Ubuntu/RHEL/etc repositories. Most likely we'll need to put them in the
ASF repository space at http://www.apache.org/dist/cassandra/ . The
alternative, I guess, would be to bundle the python-cql and python-thrift
libraries into the Cassandra packages at build time.
> Add cqlsh to deb and rpm packaging
> ----------------------------------
>
> Key: CASSANDRA-3458
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3458
> Project: Cassandra
> Issue Type: Improvement
> Components: Packaging
> Reporter: paul cannon
> Assignee: paul cannon
> Priority: Minor
>
> Once (if?) CASSANDRA-3188 is committed, cqlsh will be distributed with the
> cassandra tarballs, but not in the debs or rpms. (Actually, it looks like the
> cqlsh script will get put in the rpm by accident, but not its associated
> libraries).
> We might even want to break cqlsh out into a separate package from the same
> source, so that it can be installed on machines only intended to be used as
> cassandra clients, not servers.
> Maybe that doesn't make sense without including nodetool and cassandra-cli
> too, and then we'd need yet another package to hold the jars that are common
> between cassandra and cassandra-client... maybe it's not worth it for now.
> Either way, make sure installing cassandra debs and rpms ends up with a
> working cqlsh.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
