cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stu Hood (JIRA)" <>
Subject [jira] Updated: (CASSANDRA-786) RPM Packages
Date Sat, 27 Feb 2010 20:33:05 GMT


Stu Hood updated CASSANDRA-786:

    Attachment: 768-update-spec-for-trunk.diff

> The whole point of using Ivy was to avoid the problems in redistributing third-party
binary artifacts.
Agreed... '786-trunk-jar-changes.diff' solved the problem in the wrong place. The solution
is to actually update the spec: new patch attached that removes the incubating tag and includes
the Ivy fetched jars from the correct location.

The root of the problem was that the spec was built for the 0.5 release specifically. The
attached patch makes it useful for trunk and the 0.6 release.

> RPM Packages
> ------------
>                 Key: CASSANDRA-786
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Contrib
>            Reporter: Daniel Lundin
>            Priority: Minor
>             Fix For: 0.6
>         Attachments: 768-update-spec-for-trunk.diff, 786-adjust-jars.patch, 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.

View raw message