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 (Created) (JIRA)" <ji...@apache.org> on 2011/11/04 20:45:51 UTC
[jira] [Created] (CASSANDRA-3458) Add cqlsh to deb and rpm
packaging
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
[jira] [Commented] (CASSANDRA-3458) Add cqlsh to deb and rpm
packaging
Posted by "Jonathan Ellis (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13144299#comment-13144299 ]
Jonathan Ellis commented on CASSANDRA-3458:
-------------------------------------------
I'm fine w/ the quick + dirty shove-it-all-in-the-main-deb approach for now. Also agree that ultimately it would be good to split out cqlsh + cli + nodetool.
> 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
[jira] [Commented] (CASSANDRA-3458) Add cqlsh to deb and rpm
packaging
Posted by "Eric Evans (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13174464#comment-13174464 ]
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}} dependencies.
I don't think this makes any real difference for the platforms we're running on, but it's more inline with best practice (http://wiki.debian.org/Python/Policy), 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: https://issues.apache.org/jira/browse/CASSANDRA-3458
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-3458) Add cqlsh to deb and rpm
packaging
Posted by "paul cannon (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
paul cannon updated CASSANDRA-3458:
-----------------------------------
Affects Version/s: 1.0.3
Fix Version/s: 1.0.4
> 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
> Affects Versions: 1.0.3
> Reporter: paul cannon
> Assignee: paul cannon
> Priority: Minor
> Fix For: 1.0.4
>
> 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
[jira] [Commented] (CASSANDRA-3458) Add cqlsh to deb and rpm
packaging
Posted by "paul cannon (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13146451#comment-13146451 ]
paul cannon commented on CASSANDRA-3458:
----------------------------------------
Yeah, probably not a big deal. Just didn't know how much of a pain it would be to make changes to the release process.
> 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
[jira] [Commented] (CASSANDRA-3458) Add cqlsh to deb and rpm
packaging
Posted by "paul cannon (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (CASSANDRA-3458) Add cqlsh to deb and rpm
packaging
Posted by "Jonathan Ellis (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13146420#comment-13146420 ]
Jonathan Ellis commented on CASSANDRA-3458:
-------------------------------------------
bq. Most likely we'll need to put them in the ASF repository space at http://www.apache.org/dist/cassandra
Isn't that where people are going to be getting the Cassandra deb from anyway? Doesn't sound like a big deal to me.
> 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
[jira] [Updated] (CASSANDRA-3458) Add cqlsh to deb and rpm
packaging
Posted by "paul cannon (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
paul cannon updated CASSANDRA-3458:
-----------------------------------
Attachment: (was: 3458.patch-debian.txt)
> 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
> Affects Versions: 1.0.3
> Reporter: paul cannon
> Assignee: paul cannon
> Priority: Minor
> Fix For: 1.1
>
>
> 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
[jira] [Commented] (CASSANDRA-3458) Add cqlsh to deb and rpm
packaging
Posted by "Eric Evans (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13174465#comment-13174465 ]
Eric Evans commented on CASSANDRA-3458:
---------------------------------------
Oh, and I'm not sure if we should expect a patch to the RPM, so I'm leaving this open. Feel free to close it if that's not happening.
> 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
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-3458) Add cqlsh to deb and rpm
packaging
Posted by "Jonathan Ellis (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-3458:
--------------------------------------
Reviewer: urandom
> 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
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-3458) Add cqlsh to deb and rpm
packaging
Posted by "paul cannon (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
paul cannon updated CASSANDRA-3458:
-----------------------------------
Fix Version/s: (was: 1.0.8)
1.1
> 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
> Affects Versions: 1.0.3
> Reporter: paul cannon
> Assignee: paul cannon
> Priority: Minor
> Fix For: 1.1
>
> 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
[jira] [Updated] (CASSANDRA-3458) Add cqlsh to deb and rpm
packaging
Posted by "paul cannon (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
paul cannon updated CASSANDRA-3458:
-----------------------------------
Attachment: 0001-add-cqlsh-to-Debian-package.patch.txt
Updated patch applies against trunk, AFTER applying the patch from CASSANDRA-3507.
Now ships bundled python-cql and thrift libraries in deb, in accordance with the 3507 approach.
For better convenience, use my 3458 branch at
https://github.com/thepaul/cassandra/tree/3458
(commit 0a9555e3f596c340ab9c8f648919bbfbf3b85841, in case the branch goes away or changes).
> 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
> Affects Versions: 1.0.3
> Reporter: paul cannon
> Assignee: paul cannon
> Priority: Minor
> Fix For: 1.1
>
> Attachments: 0001-add-cqlsh-to-Debian-package.patch.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
[jira] [Commented] (CASSANDRA-3458) Add cqlsh to deb and rpm
packaging
Posted by "paul cannon (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13151428#comment-13151428 ]
paul cannon commented on CASSANDRA-3458:
----------------------------------------
I'm going to just punt on adding cqlsh to the rpm for now. The existing spec file is already way out of date and probably unworking, and it doesn't seem right to put in the work to fix it up under the rubric of this ticket. Can we just commit the addition to the deb for now?
> 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
[jira] [Updated] (CASSANDRA-3458) Add cqlsh to deb and rpm
packaging
Posted by "paul cannon (Updated) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Reopened] (CASSANDRA-3458) Add cqlsh to deb and rpm
packaging
Posted by "Sylvain Lebresne (Reopened) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sylvain Lebresne reopened CASSANDRA-3458:
-----------------------------------------
I've reverted this because I personally don't feel we've fully settled on CASSANDRA-3507 and in the meantime this block a potential release of 1.0.7.
As a side note, I don't see the rush of committing this in minor release. 1.1 is not that far away now and if we're going to include cqlsh in-tree it'll have more publicity if it's added as a new feature of 1.1 than if it's shoved in some obscure version number.
> 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
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira