[
https://issues.apache.org/jira/browse/CASSANDRA-786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12838019#action_12838019
]
Eric Evans commented on CASSANDRA-786:
--------------------------------------
Skimming through the patch I noticed lines like ...
%setup -q -n apache-cassandra-incubating-%{dist_version}-src
... that make me think this needs to be updated, (the `incubating' suffix has
been removed).
Also, I'm not sure if 786-trunk-jar-changes.diff was meant to be applied to the
build.xml in svn, or to be applied during the RPM build, but if it's the
former, than consider this a -1 for that patch. The whole point of using Ivy
was to avoid the problems in redistributing third-party binary artifacts.
> RPM Packages
> ------------
>
> Key: CASSANDRA-786
> URL: https://issues.apache.org/jira/browse/CASSANDRA-786
> Project: Cassandra
> Issue Type: Improvement
> Components: Contrib
> Reporter: Daniel Lundin
> Priority: Minor
> Fix For: 0.6
>
> Attachments: 786-trunk-jar-changes.diff, cassandra.spec
>
>
> RPM packages (and debs of course) would be nice,especially now that cassandra
> is maturing and gaining more interest.
> Lowering the threshold for getting cassandra running and getting started is
> also important.
> I think the RabbitMQ project has an admirable "Download and install"
> experience, not to mention the rather cute "2 min guarantee". Definitely a
> good inspiration.
> I've been studying Cloudera's Hadoop packages, which are very nice, and
> really appreciate the separate packages for configuration.
> This allows easy deployment of node configuration to a cluster.
> I'll have a spec file for building RHEL5 / CentOS packages ready for review
> and attached here in a bit.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
