You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "paul cannon (Updated) (JIRA)" <ji...@apache.org> on 2011/11/16 20:02:51 UTC

[jira] [Updated] (CASSANDRA-3458) Add cqlsh to deb and rpm packaging

     [ https://issues.apache.org/jira/browse/CASSANDRA-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

paul cannon updated CASSANDRA-3458:
-----------------------------------

    Attachment: 3458.patch-debian.txt

This adds cqlsh to the Debian packaging, and adds the necessary dependencies on python and python-cql for cassandra.

NOTE that the next time we build and distribute official cassandra debs, we should now make python-cql and python-thrift available in the same area.
                
> 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
>         Attachments: 3458.patch-debian.txt
>
>
> 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