On 5/12/06, Paul Howarth <paul@xxxxxxxxxxxx> wrote:
The list of problems on the JavaFAQ page relates to the native Java implementation using gcj, not Sun Java. The link Dan referred to for the "JPackage method" shows how to install Sun Java in a way that coexists
This method does make the assumption that someone wants both Java implementations and wants more than the JRE. I would doubt those are good assumptions for new users. The "install to /opt" option is just a 16MB download and 5 minutes of configuration, whereas the above requires 45MB JDK download, repackaging and yum installing for a 132MB of packages to install. I would say thats a bit excessive (possibly unnecessary) for new users. For coexisting, the /opt method co-exists very nicely. It would be just better to say: "DO NOT install the Sun RPM" and/or "Java DEVELOPMENT in FC4+ highly recommends Jpackage setup". Which makes perfect sense as it casts a distinction between developers and common endusers. Maybe someone should add to the FAQ: Do I need both the Runtime and the Compiler? Or something to that effect. There just seems to be some ambiguity there.
nicely with other java implementations you might install, and is managed using rpm just like most of the other software on the system.
Managed like other rpms ... So if sun put out a 5.0 Update 7 for security tomorrow would I not be required to repeat the whole process of compilation from another 45MB download?
Installing Java "the JPackage way" also has the benefit of making available the large number of ready-packaged Java applications in the JPackage repository, which is very useful if your interest in Java stems from more than just the browser plugin.
If I were to guess, majority of people are interested in merely the JRE. Don't misunderstand me, the jpackage solution is well done. This is just my opinion based on what's practical for general recommendations. -Mauriat
