When uninstalling the Tiger JRE/JDK RPM on Linux from builds prior to b50 (i.e. the directory name change), the GNOME association files can be removed even if a post b50 Tiger build is still installed.

This happens when there are only b49- and b50+ RPM builds installed.  If there is also a 1.4.2 RPM installed when the b49- build is removed, then this does not occur.

What happens is that when the RPM uninstall is run (ex.: rpm -e j2re), a check is made to determine if there are any remaining supported JRE/JDK installs.  Prior to b50, this test checks for supported installs by looking in /usr/java for directories with the patterns j2re<version> and/or j2sdk<version>, and accepting version 1.4.2 or higher.  This check does not recognize the new directory name patterns of jre<version> and jdk<version>, so when these older RPM installations are removed, they incorrectly remove the GNOME association files.

The GNOME association files are:

    ${GNOMEDIR}/share/mime-info/java-archive.keys
    ${GNOMEDIR}/share/mime-info/java-archive.mime
    ${GNOMEDIR}/share/application-registry/java-archive.applications
    ${GNOMEDIR}/share/mime-info/java-web-start.keys
    ${GNOMEDIR}/share/mime-info/java-web-start.mime
    ${GNOMEDIR}/share/application-registry/java-web-start.applications

If GNOMEDIR is not set, it defaults to /usr.

If these files are missing, the user will be unable to run a JAR or JNLP file by double-clicking the file's icon in Linux.  It may also affect the browser's ability to launch files of these types.  (Note: this should not affect Netscape/Mozilla browsers, which use a separate association method.)

The files can be restored by removing, and then re-installing the RPM.

This bug will be resolved by adding a Release Note to Tiger.  Closing as
'not-a-but' ... in the codebase.

  xxxxx@xxxxx   2004-06-18