On 02/19/2012 05:44 PM, Darrell Anderson wrote:
> Required? Maybe. Maybe not. :) I don't use any of those options. I'm not a gadget freak and don't carry my life around in a gadget. I also am a privacy advocate and will never post private information on any online service or cloud server. Yeah, I'm weird. ;) I also see many home users not needing those options. Nonetheless, I build my packages with those features because others use my packages.
> 

I'm not really in love with gadgets myself, but for basic "when it gets entered
on my calendar at the office it shows up on my desktop/device" regardless where
I am -- or when I'm asked "does this day work with you?" -- it is pretty much
what is expected today. With caldav built into TDE, then kdepim or other apps
would have this native capability. Granted, there are many desktop tools that
can do this, but to continue with kde <= 3 philosophy of providing
top-of-the-line no-frills capability, the 'davs' get my vote for being a part of
that 'good core functionality'

Don't get me wrong. I'm not arguing with you about them, I'm just providing
background as to why I have found the 'davs' (which are pretty obscure pieces of
code) indispensable. Not that they are immediately usable by every desktop user,
but because they provide a means to integrating the desktop with remote calendar
and contact servers and provide a 'toolset' for developing pretty neat features
in the years to come.

I don't know what Tim's motivation was for moving them into dependencies, but I
agree with it :)

> If you look at the commit log for the 16th, you'll see that Tim moved those two packages to the dependencies tree. I presume they remain optional dependencies like avahi-tqt, but no longer are those packages cleverly hidden deep in Tim's web site. :)
> 
> Darrell

I have caldav built, I'm still working on carddav.

-- 
David C. Rankin, J.D.,P.E.