You can always find the newest version of the software at ftp://linux.in-berlin.de/pub/pilot/pi-address.tar.gz. This is a symbolic link to the actual archive pi-address-0.x.y.tar.gz
There is a mirror site at ftp://walther.in-berlin.de/pub/pilot/. In case you have trouble to connect to the primary ftp server, try this one instead.
For people in the US maybe this mirror will be much faster: ftp://pv915.pv.reshsg.uci.edu/pub/pilot/.
Both above mentioned mirror sites usually are updated within hours after announcing a new release.
If you are willing to setup another mirror site for pi-address please contact the author.
You can find precompiled binaries (linked dynamically against libqt.so) at ftp://linux.in-berlin.de/pilot/binaries/ for the following platforms:
If you find any problems using one of these binaries, please email the author with a detailed description of the problems.
Alan Harder, the maintainer of PilotManager, is providing a precompiled binary for Solaris on his webpage http://www.moshpit.org/pilotmgr/binaries/misc/ (statically linked against pilot-link.a and libqt.a).
No, not yet. If you are willing to maintain a Debian package please contact the author. Any help will be appreciated.
Yes, Jon Lasser is maintaining a RPM package. There is a subdirectory ftp://linux.in-berlin.de/pub/pilot/rpm/ on the primary ftp site. You can find the RPM package on RedHatīs ftp site too.
Follow the instructions in the README file. Make sure that the include files and libraries for libqt.so and libpisock.a can be found.
Both pilot-link.0.8.9, pilot-link.0.8.11 and pilot-link.0.8.13 have been tested and are known to work.
gcc 2.7.2 and 2.8.1 have been tested on Linux and Solaris.
The authors plan is to use GNU autoconf for configuring the package. This would be the best solution for solving problems in finding header files and libraries. The only problem is the lack of spare time...
This was the only way, the author could figure out how to link one of the libraries dynamically (Qt) and the other statically (libpisock.a). If anybody knows of another solution for this, please email the author.
In general pi-address does not rely on a specific directory.
Just copy the binary to any directory which is appropriate for your system. There is a install target in the Makefile, check the variable $prefix in the Makefile, change if necessary and run make install. Depending on the directory where you want to install you may need root privileges.
The FAQ files can be accessed online by chosing Help / FAQ from the menubar.
There is an install-doc target in the Makefile, check the variable $doc_prefix in the Makefile, change if necessary and run make install-doc. This target is also run if a make install is done. Donīt forget to specify this new path in your configuration file for your HelpApplication. Depending on the directory where you want to install you may need root privileges.
Specifying an empty entry for HelpApplication disables the menu Help / FAQ.
Starting with V0.1.2 there is a configuration file for the program. On startup the program searches and reads the configuration file in the following places (and in that order):
The package provides an example configuration file with the program's default values. It's documented so the meanings of the key/value pairs should be obvious.