- add kFreeBSD to NBI and CPUID
- add kFreeBSD to jcpuid/jbigi build scripts
- refresh debian patches to compensate for kFreeBSD changes
- i2prouter: Detect kFreeBSD and normalize its name
- clean up osid (switching to "elif") and adding support for detecting kFreeBSD
- update postinstall.sh; I2P cannot be installed using gij so postinstall.sh
will not be run. If/when openjdk finally comes to kFreeBSD, we'll be ready for it.
In my testing:
32 bit Windows (and, of course, 32 bit JRE) = Java added to the PATH
64 bit Windows and 64 bit JRE = Java added to the PATH
64 bit Windows and 32 bit JRE = Java *not* added to the PATH.
So...with this check-in:
- If the environment variable JAVA is set in the script, we'll use that
manually specified Java. We will not look in the registry, but we'll check to
make sure that the binary exists.
- If Java is found in the system path, we'll use it instead. We will not look in the
registry.
- If the variable is not set manually and Java is not in the system path we'll
look in the registry to find the java binary.
I've tested this in Windows XP, Vista, and 7 but it should work in any supported version
of Windows.
Let's not direct people to see how to configure their browser at
http://www.i2p2.i2p/htproxyports when you need to have your proxy configured to go there!
Footer hidden when embedded because of margin issues, and out-of-place-ness.
Have confirmed that susi's opinion when the themes were initially updated was
"do what you want", so no legal problem.
in configfile will only work on older launchd version. Ref manpage:
(-w Overrides the Disabled key and sets it to false. In previous ver-
sions, this option would modify the configuration file. Now the
state of the Disabled key is stored elsewhere on-disk.)
the old version (grep -o '[0-9]*\.[0-9]*\.[0-9]*') won't detect versions as 10.8, or 10.7
added cut -d: -f2 | sed -e 's/[^0-9]*//' , matching both 10.8, 10.7.4, etc.