Bug#268214: /etc/.java/

[Juergen Kreileder]

,----[ Patch from Alex Owen <owen@cus.org.uk> ]
| --- lib/j2se.sh.orig    2004-09-13 07:53:22.000000000 +0100
| +++ lib/j2se.sh 2004-10-05 21:57:54.000000000 +0100
| @@ -132,6 +132,8 @@
|      # Problem: dh_installchangelogs thinks this is a native package.
|      echo "    dh_installdocs"
|      dh_installdocs
| +    echo "    dh_installdirs"
| +    dh_installdirs etc/.java/.systemPrefs
|      # dh_install
|      # dh_link
|      echo "    dh_strip"
`----

You should also create two empty files in /etc/.java/.systemPrefs

$ ls -al /etc/.java/.systemPrefs        
total 8
drwxr-xr-x  2 root root 4096 Jul 26 22:38 ./
drwxr-xr-x  3 root root 4096 Jul 26 22:38 ../
-rw-r--r--  1 root root    0 Jul 26 22:38 .system.lock
-rw-r--r--  1 root root    0 Jul 26 22:38 .systemRootModFile


,----[ Comment from Jerry Haltom <jhaltom@feedbackplusinc.com> ]
| I would suggest using /etc/java instead for policy reasons, but the rest
| stands.

Technically /etc/java would be nicer, but Sun chose /etc/.java for
its JVM and derived implementations (like Blackdown's and IBM's) use
the same for the sake of compatibility.
 
| I do however think it is easier to just create a symlink in the JRE_HOME
| from .systemPrefs to /etc/java/systemPrefs and give root write access.
`----

I think /etc/.java and it's contents should be proper directories and
files.  The two files listed above should be conffiles (they are in
our new packages for Debian).

Note that the distribution-independent installers from Sun and
Blackdown create the files listed above if they don't already exist in
/etc/.java/.systemPrefs when the installer is run by root.
(They only get created inside the just installed JRE tree if the
installer is not run by root.)


        Juergen

-- 
Juergen Kreileder, Blackdown Java-Linux Team
http://www.blackdown.org/java-linux/java2-status/