>> A heavily patched libical was originally included as part
>> of the kdepim
>> source code.  For the Trinity project this was split
>> into an external
>> dependency, as other programs also use libical and there
>> was no more need
>> for the KDE-specific patches to the upstream code. 
>> This is a dependency
>> that will need to be filled even for basic functionality.
>>
>> libcaldav and libcarddav are for the new CalDAV and CardDAV
>> resources, for
>> korganizer and kaddressbook respectively.  You can
>> disable them, but you
>> will lose interoperability with newer PIM suites such as
>> Google Calendar
>> and Zimbra.
>
> So libical is required and is a replacement for libkcal?

Yes.  It is used by libkcal though; it is a replacement for the old
internal version of libical.  Trust me; it's much better this way--the old
integrated libical had many bugs, including random changing of Korganizer
appointment times.

>
> What about libcaldav? libcarddav? Are there configure options to disable
> the latter two?

The resources that use them *should* shut down automatically when those
libraries are not detected.  If this does not occur, let me know and I
will fix it ASAP.

>
> I checked configure --help and saw nothing obvious for all three. :(
>
> I don't see the links for the libcaldav and libcarddav sources. I saw
> links to deb packages.

Look for the .tar.gz file--it is in that list somewhere.

>
> Note: Just about everything I select at your quickbuild site uses an
> "invalid certificate." I hate this so-called feature of Firefox. I know
> how to add exceptions, but would be nice if folks did not have to do that.
> :)

Yes it would.  However, security certificates cost money.  Lots of it. 
Unless someone would like to donate a site-wide certificate for
*.quickbuild.pearsoncomputing.net, I don't think that will change. ;-)

Tim