This is kind of a work in progress. Here's what we've done so far to
build a portable tarball. We keep all the stuff that Citadel needs, but
is not part of Citadel itself, in /usr/local/ctdlsupport, and we keep
-Citadel in /usr/local/citadel.
+Citadel in /usr/local/citadel. (This is only known to work on Linux+GCC.)
We build in /usr/src.
possible to build RPM's, and bring the installation process closer to that
of other packages, which if you're using the new configure script goes
like this:
- ./configure [--enable-ansi-color] [--disable-auto-login] [--prefix=/foo]
-
+ ./configure [--enable-ansi-color] [--disable-autologin] [--prefix=/foo]
- --prefix specifies the location the BBS will run from,
+ --prefix specifies the location Citadel will run from,
/usr/local/citadel by default.
to build a highly optimized version without debugging symbols, you could
do something like this (with the bourne shell):
Status: full functionlity is present in the current implementation, including
the ability to keep a personal calendar, send/receive invitations, manage
attendees, check free/busy times, etc. It is fully usable via WebCit
- and also works with Kolab-compatible clients (vCalendar over IMAP for the
+ and also works with both Aethera and Kolab1 (vCalendar over IMAP for the
calendar store, and vCalendar over HTTPS for checking other users' free/busy
times).
Items recently removed from TODO list
-------------------------------------
-* WebCit support for HTTP transactions performed by Kolab clients
- (The current WebCit build works with the KDE Kolab klient using HTTPS.)
+* WebCit support for HTTP transactions performed by Kolab1 clients
+ (The current WebCit build works with the Kolab1 klient, and with Aethera,
+ both using HTTPS.)
* RFC 2739 compliance (provide calendar free/busy URL's in vCard and LDAP)
(If anyone knows of clients that make use of this, let us know / test it)