Please follow the download and install instructions at
http://www.moshpit.org/pilotmgr/download.html

If precompiled binaries are available for your OS/architecture and perl
version then the page above should have all the info you need.  However,
if you need to compile and install any of the perl modules yourself then
this file contains the info you need....

-------------------------------------------------------------------------
PilotManager, being that it's written in Perl, is very portable
to other platforms.  The installation notes below are incomplete,
but they should get you to the point where the GUI actually comes
up on your system.  Good luck.

Installation Notes
==================

To save space, the packages that PilotManager depends upon have not
been included in this package.  You will need to download them and 
install them in order to use this package.

This is not a particularly difficult, but it's not trivial either.
Someday I'll simplify this process, but considering how many packages 
this depends on, it's always going to take time to get it all
installed. 

Packages
--------

1.Perl			[v5.003 or later]

	You must have a working version of Perl, preferably v5.003 or
	later installed on the system.

	You can obtain the latest copy of Perl from your nearest
	CPAN site.  If you don't know where to find CPAN, try:

			http://www.perl.com/


2. pilot-link 		[v0.8.4 or later]

	You can obtain the latest copy of pilot-link from:

		ftp://ryeham.ee.ryerson.ca/pub/PalmOS/

	You must configure and install pilot-link, then configure
	and install PDA::Pilot (the perl5 interface to pilot-link).

		% cd pilot-link.0.8.9
		% configure
		% make install
		% cd Perl5
		% perl Makefile.PL
		% make install

	FYI, for the sun4-solaris distribution of PilotManager pilot-link
	was built without debugging info (-g flag removed from Makefile
	and libsock/Makefile after configure step) and libpisock was
	statically linked to Pilot.so instead of dynamically linked
	(modified Makefile after perl Makefile.PL step)

3. Perl modules

	You can obtain the following Perl modules from CPAN (see above).
	You'll need to configure, build and install these packages on your
	system.  You can check if you already have a package installed
	like this:
	   % perl -e "use Tk"
	   % perl -e "use Data::Dumper"

	These modules are *required* for using PilotManager:
	   -  Tk module			[v400.202 or later]
	   -  Data::Dumper module	[v2.07 or later]
	      (NOTE: Data::Dumper comes standard with perl 5.004_71 and later)

	These modules are required only for using the specified conduits:
	   -  Calendar::CSA module	[v0.07 or later]
	      This module is required ONLY for the SyncCM conduit which
	      synchronizes with Calendar Manager (openwindows or cde)
	      calendars.  If your platform does not have CDE, you do not
	      need this package.

	   -  MD5 module		[v1.6 or later]
	   -  IO modules		[v1.15 or later]
	      These modules are required only for the SyncPlan conduit which
	      synchronizes with the Plan calendar package.  SyncPlan uses
	      IO::Socket and IO::Select from the IO modules package.


Making a Release
================

Once you have finished compiling PilotManager for your platform, you
should get in touch with me and coordinate releasing your port.  I'd
like to keep track of the PilotManager porters so that when there's a
new source release we can get new versions out for different platforms
relatively quickly.  

Making a binary release is a bit tricky.  There's a sparse Perl 
library installed under the pilotmgr/lib directory.  You'll need to
populate your arch's section of the libraries.  If you're a perl guru,
this is easy.  If not, check out one of the prepackaged binary releases.

More on making releases later.


Happy hacking,
Alan.Harder@Sun.Com
Bharat@Menalto.Com