
All of the conduits and some of the utilities now make use of a
central option registry (see PDA.Pilot.Conduit.Config for the class
definition).  Until complete documentation for this package is
written, this file will document the available options.

The Conduit.Config module looks for options in three places, in order:

    /var/local/pilot/<username>/Options.pyk
      (Saved state, not user editable)
    /var/local/pilot/<username>/Options.py
    ~/.pdapilot

The latter two files are executable Python code, which is run in its
own namespace with two variables set: user, which is the username (or
None if it is not yet known), and Options, which is a Registry
object.  To set an option, put in a line like "Options.set(group,
option, value)".

Programs which connect to the Pilot will generally read the options
twice.  The first time, only ~/.pdapilot will be looked at, with
user==None, to pick up any default port settings and the like.  Once
the Pilot's user name is retrieved, all three option files are read
again.

Group: 'General'

  'username': A default user name, for use by programs which do not
      connect to the Pilot.

  'pilot_port': The path to the device the Pilot is connected to.
      Usually defaults to /dev/pilot.

Group: 'HotSync'

  'conduits': A list of conduit names, each of which will be activated
      in order during sync.

Group: 'Conduit/Backup'

  'backup_dir': The directory to locate the backup in.  Defaults to
      /var/local/pilot/<username>/backup.

  'ignore_backup_bit': If true (which is the default), considers all
      databases for backup.  If false, only considers those which have
      the backup bit set.

  'incremental': If true (which is the default), only backs up
      databases which have been changed (according to time stamps)
      since the last backup.

Group 'Conduit/Install'

  'install_dir': The directory in which to look for databases to
      install.  Defaults to /var/local/pilot/<username>/install.

