[
https://issues.apache.org/jira/browse/CASSANDRA-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973954#action_12973954
]
Eric Evans commented on CASSANDRA-1890:
---------------------------------------
Technically, the release is meant for packaging. So that an upstream version
like 0.7.0~rc3 could have multiple RPM package releases, 0.7.0~rc3-1,
0.7.0~rc3-2, 0.7.0~rc3-3, etc. But, that only really matters if someone is
doing that, and I don't think they are.
I'm going to commit this on the basis that it leaves the spec file in a better
state than it is now, but I'll leave the ticket open in case there is any
discussion that needs to be had over the way versioning is handled.
> Updates and tweaks to spec file for easier support of candidate and beta
> releases
> ---------------------------------------------------------------------------------
>
> Key: CASSANDRA-1890
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1890
> Project: Cassandra
> Issue Type: Improvement
> Affects Versions: 0.7 beta 1, 0.7 beta 2, 0.7 beta 3, 0.7.0 rc 1, 0.7.0 rc
> 2
> Reporter: Nate McCall
> Assignee: Nate McCall
> Fix For: 0.7.0
>
> Attachments: 1890.txt
>
>
> Updates URL, license declaration. Add conflicts and obsoletes tags for
> existing RPM packages. Removed JNA dependency as that is not on stock yum
> repos. Unfortunately, yum does not widely support conditional Requires
> extensions yet.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
