Re: java again really

Karl Larsen wrote:

Peter Boy wrote:

Am Samstag, den 05.01.2008, 06:18 -0700 schrieb Karl Larsen:

OK. I am confused. You say there is now ready to yum a jpackage for F8 that has the infrastructer for using the d/l Sun java. This is what I decided was needed. So please if you can give us the way to yum this file(s).

    I hope it is not the same files F8 comes with :-)

check weather jpackage-util is installed on your machine an then visit
www.jpackage.org/yum.php

Or just download the appropriate
java-1.x.x-sun-compat-1.x.x.y-zjpp.i[nnn}.rpm, which corresponds to the
Sun Java version you are using. and install it

e.g. http://www.jpackage.org/browser/rpm.php?jppversion=5.0&id=489


Peter

   Well I looked for jpackage-util and got this:

[root@k5di ~]# yum install jpackage-util
Setting up Install Process
Parsing package install arguments
No package jpackage-util available.
Nothing to do
[root@k5di ~]#

Then went to the web page and it has a special file for getting to the jpackage.repo which I balk at because new repo's are not good as a rule. Since I did set up my java in a manual way I'm not sure I want to mess up what works :-)

Karl

       Installing the Sun JDK using the '-compat' method

  1.

     Get the Sun JDK 5.0 from:

     http://java.sun.com/javase/downloads/index.jsp

     by choosing the "JDK 5.0 Update N" "Download" button, and then
     choosing "RPM in self-extracting file" for Linux on the page that
     displays after pressing the button.

     /Important:/ Do NOT install the "Linux x64" version of the SDK.

     If you prefer the older Java 1.4.2 SDK, get it from:

     http://java.sun.com/j2se/1.4.2/download.html

     by choosing the "Download J2SE SDK" link and from there the "RPM
     in self-extracting file" for Linux.

  2.

     Install java-1.4.2-sun-compat or java-1.5.0-sun-compat

     Download and install the appropriate -compat RPM from JPackage at:

     ftp://jpackage.hmdc.harvard.edu/JPackage/1.7/generic/RPMS.non-free/

     Make sure to match the version of the -compat package to the SDK
     you've installed in the first step. The -compat RPM requires that
     the RPM self-extracting file from Sun be used in the previous
     step, not the plain (non-RPM) one.

     For instance, for a Sun SDK 1.5.0_08 you should get:

     ftp://jpackage.hmdc.harvard.edu/JPackage/1.7/generic/RPMS.non-free/java-1.5.0-sun-compat-1.5.0.08-1jpp.noarch.rpm

     and for a Sun SDK 1.4.2_12 you should use:

     ftp://jpackage.hmdc.harvard.edu/JPackage/1.7/generic/RPMS.non-free/java-1.4.2-sun-compat-1.4.2.12-1jpp.i586.rpm

  3.

     Selecting alternatives for java and javac.

     The alternatives system allows different versions of Java from
     different sources to co-exist on your system. You should make sure
     the one you want is selected so that SysV service scripts use that
     one. This is also needed if you want the installed SDK to be the
     default java and javac on the system. Note that this choice can
     often be overridden by setting the JAVA_HOME environment variable.

     If you are rebuilding packages that require Java 5 to build but
     generate code that is capable of running in JDK 1.4 as well, you
     probably should also set java_sdk_1.4.2 to the Java 1.4 JDK you
     have installed, from the same provider of your Java 5 one.

     As root, issue the following command:

            	/usr/sbin/alternatives --config java

     and make sure the Sun one is selected (marked with a '+'), or
     select it by entering its number as prompted.

     Make sure you do the same for javac (and java_sdk_1.4.2" if
     needed). We recommend that all alternatives point to the same
     manufacturer.


     Get the package you're looking for

------------------------------------------------------------------------

Karl

--

	Karl F. Larsen, AKA K5DI
	Linux User
	#450462   http://counter.li.org.
  PGP 4208 4D6E 595F 22B9 FF1C  ECB6 4A3C 2C54 FE23 53A7