[
https://issues.apache.org/jira/browse/CASSANDRA-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12931078#action_12931078
]
Nick Bailey commented on CASSANDRA-1726:
----------------------------------------
bq. Can you explain what you mean by this?
Well I'm not sure if it is a convention, but I usually find it is good to
install default configuration for packages using the update-alternatives
command. That way the default configuration can be installed with a low
priority and anyone who wants to manage their cluster configuration through
packaging can install an alternative configuration with a higher priority.
With the current package, any manual edits to configuration will be overwritten
when the cassandra package is updated (At least I think they will, thats how
the rpm packages work). The rpm packages already work this way.
bq. It probably needs to be brought up to date with recent changes, but so long
as bin/cassandra is shipped in the package as /usr/sbin/cassandra (as an
alternative to the init script), then I'm not sure how you could remove it.
I'm just not sure why its installed from debian/cassandra.in.sh instead of
bin/cassandra.in.sh? That just means it gets behind on changes right?
> Update debian packaging to use alternatives
> -------------------------------------------
>
> Key: CASSANDRA-1726
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1726
> Project: Cassandra
> Issue Type: Improvement
> Components: Packaging
> Affects Versions: 0.7.0
> Reporter: Nick Bailey
> Priority: Minor
> Fix For: 0.7.1
>
>
> We should update the debian packaging to install configuration using
> alternatives. Additionally we can probably get rid of the custom
> cassandra.in.sh for debian packaging.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
