On 31/12/12 21:40, Eric Fernandez wrote:
2012/12/31 Allan McRae <allan@archlinux.org>:
It has been there for years.
Allan
Well, I discussed the issue there: https://bbs.archlinux.org/viewtopic.php?id=137555 in March 2012. I am absolutely positive that there was an issue if JAVA_HOME was not previously set (and java-environment had not been installed), and that source /etc/profile.d/jdk.sh was fixing it. Any other idea this was causing it? I'll try to see if I can reproduce it on a virtual environment.
Eric
Many Arch PKGBUILDs use JAVA_HOME, and all Arch packages are build in a minimal chroot that will require java to be installed. There is only one Arch package that sources anything to get JAVA_HOME and that is because it unsets it first (for some unknown reason...). Allan