[
https://issues.apache.org/jira/browse/CASSANDRA-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973949#action_12973949
]
Nick Bailey commented on CASSANDRA-1890:
----------------------------------------
Didn't know you could set the release to 'rc3'. How does that handle upgrading
the release? When 0.7.0 comes out is release 1 higher than rc3? I'm not sure
if its worth putting rc3 in the spec file unless we plan on updating it every
time a new beta/rc/major/minor release comes out. Should that just be left up
to whoever is building the package?
Optionally we could require the release to be passed in so someone blindly
building the spec file will have to specify it.
> 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.
