Source: infotrope-acapd
Section: mail
Priority: extra
Maintainer: Dave Cridland <dave@cridland.net>
Standards-Version: 3.6.1.1
Build-Depends: libexpat1-dev, libsasl2-dev, libssl-dev, debhelper (>= 4)

Package: infotrope-acapd
Architecture: any
Depends: ${misc:Depends}, ${shlibs:Depends}, ${perl:Depends}
Suggests: sasl2-bin
Description: Infotrope ACAP Server
 An Application Configuration Access Protocol server is a lightweight,
 schemaless database, with no validation, a heirarchical structure, full
 per-user storage, highly specific notifications, and internet-level
 security.
 .
 It can be used by ACAP-aware email clients and browsers to store, share
 and access information such as preferences, server information, bookmarks,
 personal addressbooks, and other similar data, in a fully interoperable way,
 and able to be centrally administered, to reduce administration load.
 .
 In addition, the protocol allows each application to store its own, specific,
 data, all without any changes to the server.
 .
 This package contains the Infotrope Project's implementation, which is
 believed to be conformant to RFC2244, and RFC2595, and as such is your
 only option if you want to use ACAP.
 .
 To make use of ACAP, you'll need a client capable of using it, such as Eudora,
 Mulberry, or Polymer, the latter being GPL.
