IMHO, having the information panel ("To start I2P, etc.") displayed at the end
of the installation process makes a lot more sense.
Hopefully others agree...
Compiled on trimslice
gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-8ubuntu4)
java version "1.6.0_18"
OpenJDK Runtime Environment (IcedTea6 1.8.8) (6b18-1.8.8-0ubuntu1~11.04.1)
OpenJDK Zero VM (build 14.0-b16, mixed mode)
Wrapper 3.5.12 GPLv2
All binaries stripped.
Upgrading our wrapper to 3.5.12 to fix the upstream wrapper's umask bug. All
binaries are from the delta pack except for Win64, FreeBSD, Linux ARM, and OSX
(See history.txt for more info).
The upstream script has support for Ubuntu but not Debian. This change allows
the same methods used for Ubuntu to be used for Debian. This *should* work for
any version of Linux that has Debian in its family tree.
With this check-in comes an update of our i2prouter script based upon the
script src/bin/sh.script.in from the 3.5.9 source tarball of the wrapper.
Some of the benefits of this newer version include:
- logic to determine which wrapper binary to use (32bit VS 64bit) and falling
back to alternate "bitness." This would be most useful for portable packages.
- support for far more platforms and archs than the 3.1.1 based script (such as
Solaris, risc, os/390, HP-UX, AIX, mips, ia64, etc.)
- support for installing I2P as a daemon in most UNIX-based environments with
the command "i2prouter install". The installed service can be removed with
"i2prouter remove". With testing this option has been confirmed to work in
OSX, Fedora, Slackware, Debian, Ubuntu, FreeBSD, and SuSE. It does not work
in Arch Linux (yet).
These scripts are based on InstallApp-NT.bat.in and UninstallApp-NT.bat.in from
WRAPPERSRC/src/bin of version 3.5.9 of the wrapper.
Tested in XP and Win7.