cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Evans (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-1726) Update debian packaging to use alternatives
Date Thu, 11 Nov 2010 17:16:21 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12931090#action_12931090
] 

Eric Evans commented on CASSANDRA-1726:
---------------------------------------

bq. 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.

I don't know if I'd call it convention, I think Cloudera started doing this with their Hadoop
packages.  I think this would fail the Element of Least Surprise for most Debian folks.

bq. 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.

No, changes are not overwritten.  If a configuration file has an identical checksum to what
was installed (i.e. it's unmodified), then the upgrading package will overwrite it.  However
when the checksums do not match (the config _has_ been modified), then the default action
is to keep the user-modified config and install the new one with a .dpkg-new suffix.

That should be the way redhat systems work too.

bq. 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?

Because the paths need to be different from what are in {{bin/cassandra.in.sh}}. That's the
purpose of it, to abstract out the system-specific bits of {{bin/cassandra}}. Now that heap
sizes, jvm opts, etc have been moved to {{cassandra-env.sh}}, it should rarely if ever need
to be updated.

I went ahead and removed that cruft btw (r1034002).

> 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.


Mime
View raw message