I've done a little more research on this problem.
I'm now convinced that this is a Cassandra problem,
but not the problem I had originally thought.
For example, I downloaded cassandra12-1.2.15-1.noarch.rpm
and I then ran the following with the results shown:
# rpm -iv cassandra12-1.2.15-1.noarch.rpm
error: Failed dependencies:
java >= 1.6.0 is needed by cassandra12-1.2.15-1.noarch
This clearly shows that Cassandra is dependent on java, but
notice that it says nothing about openjdk. However, if I now
run
# yum install java
I see (edited)
Resolving Dependencies
--> Running transaction check
---> Package java-1.7.0-openjdk.x86_64 1:1.7.0.51-2.4.4.1.el6_5 will be
installed
This is the crux of the problem. By making Cassandra dependent on
"java", instead of "jdk" or "jre", then installing Cassandra will
always require openjdk.
One way of proving this is what I see when I run
# yum install jdk
which is
Package 2000:jdk-1.7.0_51-fcs.x86_64 already installed and latest version
That's what we want the Cassandra rpm to see. So, I'm going to try
repacking the Cassandra rpm to depend on jdk. If all goes well, this
will work, or at least let the installation get farther.
Jon Forrest
The information transmitted in this email is intended only for the person or
entity to which it is addressed, and may contain material confidential to Xoom
Corporation, and/or its subsidiary, buyindiaonline.com Inc. Any review,
retransmission, dissemination or other use of, or taking of any action in
reliance upon, this information by persons or entities other than the intended
recipient(s) is prohibited. If you received this email in error, please contact
the sender and delete the material from your files.
