>> 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.
>
> Shouldn't libical then be in the dependencies section of svn?

No.  libical is maintained upstream in a separate source control system;
the Trinity project merely uses it and does not have any control over it
(rather like Qt).

>
>> Look for the .tar.gz file--it is in that list somewhere.
>
> I'm still unclear -- are those two packages required or optional for
> building kdepim? If they are required, then like libical, shouldn't they
> be in svn/dependencies?

OK, I'm going to make them both required.  They are less than 150Kb each
when built and add significant functionality.  As these two libraries
originated within the Trinity project, and are maintained by the same, I
also agree that they should be placed in svn/dependencies.

>
> I just dislike the way Firefox does not allow the option to accept the
> certificate. Yet Another Example of Arrogant Developers.
>

Yeah, I find it annoying as well.  This looks like it might work (I
haven't tried it yet):
http://www.cs.cmu.edu/~perspectives/firefox.html

Tim