We are having some issues with naming comvention used by the Sun Java jdk rpm. I was wondering if anyone else is running into these same problems.
We maintain software including the JDKs on almost 500 Linux machines using a rpm remote package management tool. Due to various software requirements we need to maintain multiple major versions of Java on one machine. Currently we use the following Java rpm packages:
We didn't have any problems with 1.3 and 1.4 because jdk and j2sdk are unique rpm names, but then when 1.5 came out using the jdk name again it became a direct upgrade to jdk 1.3 which cause 1.3 to be uninstalled under normal conditons so we had to code in exceptions in our installation routines, and now with jdk 1.6 coming out using the same name as well it is causing us even more problems. One of them being that once a newer jdk is installed our autoupdate program will no longer download an update to an older jdk because thinks you already have a newer one. For example, if you have jdk-1.5.0_07 and jdk-1.6.0 installed it will not automatically download jdk-1.5.0_08 when we make that available on our distributin server. If the rpms had been named jdk5 and jdk6 for instance, we would not be having any problems because they would be unique packages.
So, the question is: has anyone else ran into this problem? Has anyone repackaged the jdk yourself because of it? Any chance of getting an official Sun jdk using my proposed naming convention?
Facing the same issue. Need 2 jdks - one for the application we host and one for the monitoring software. First of all, packaged in a .bin file, which you can get around by running extract, but in the end the big issue is that both rpms name themselves "jdk" - making it hard to automate and manage what a huge pain. With different versions, you have to make sure you install both, and don't accidentally upgrade. Wish Sun would address this. Why bother making an RPM for the Linux community if it doesn't work in a practical manner?