cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Evans (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3458) Add cqlsh to deb and rpm packaging
Date Wed, 21 Dec 2011 22:31:30 GMT


Eric Evans commented on CASSANDRA-3458:

Committed with minor changes.

Specifically, the changes where to a) put a version on the {{python-support}} build dependency,
and b) to use {{${python:Depends}} } in place of the hard-coded Python and {{python-support}}

I don't think this makes any real difference for the platforms we're running on, but it's
more inline with best practice (, and maybe it'll make
things more future-proof.

If you see any problems with this, let me know!
> Add cqlsh to deb and rpm packaging
> ----------------------------------
>                 Key: CASSANDRA-3458
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Packaging
>    Affects Versions: 1.0.3
>            Reporter: paul cannon
>            Assignee: paul cannon
>            Priority: Minor
>             Fix For: 1.0.7
>         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:!default.jspa
For more information on JIRA, see:


View raw message