Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm trying to upgrade JRE 1.4.2 to JRE 1.5.0. As several people on here have seen the RPM packages have very different names (java-1_4_2-sun-1.4.2.06-1.1 vs jre-1.5.0_02-fcs). Is there a way to get the RPM software to treat the jre1.5.0 package as an upgrade for java-1.4.2 instead of the messier option of installing both and then forcing a remove on the original?
Just wondered if this was possible and whether it would leave dependencies in a cleaner state afterwards,
I think what brundles is saying is that the jre1.5 package might not be recognized as an upgrade to the installed jre1.4 package.
What you could do is install the jre1.5 package and then manually remove the jre1.4 components (it's usually in a single directory - on my system it was something like /usr/java/jre1.4.2). This way, rpm will think that jre1.4 is still there so won't complain about dependencies when something requires it. you might still have to fix some application configurations so they find the new java installation. It's not the cleanest way but it should work.
I don't think there is a way to treat the 1.5 version as an upgrade to your 1.4 version because your 1.4 version seems to be a full SDK whereas the 1.5 version is a jre. If both were jre's or sdk's, installing a newer package would theoretically delete the old one.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.