Let me add a few comments in support of packaging this for Ubuntu..
I had originally used CalDav to sync to my Google Calendars, but changed to GCALDaemon.
1. GCALDaemon allows creation of a real, accessible offline copy of your calendar (ics format),
versus the alternative for accessing Google calendars, CalDav, which does not.
Caldav provides only a 'cache' which works less well.
2. This offline copy can also be easily backed up,
whereas if you are using CalDav, you have to separately wget the google .ics files to back them up.
2. Philipp Heckel's particular packaging of it adds 2 advantages to the original GCALDaemon:
i. Configuration is kept in the home dir, where it belongs
(the original keeps it in /usr/local/sbin, no obvious way to move it)
ii. A script is provided to easily stop the daemon, not provided in the original.
Let me add a few comments in support of packaging this for Ubuntu..
I had originally used CalDav to sync to my Google Calendars, but changed to GCALDaemon.
1. GCALDaemon allows creation of a real, accessible offline copy of your calendar (ics format),
versus the alternative for accessing Google calendars, CalDav, which does not.
Caldav provides only a 'cache' which works less well.
2. This offline copy can also be easily backed up,
whereas if you are using CalDav, you have to separately wget the google .ics files to back them up.
2. Philipp Heckel's particular packaging of it adds 2 advantages to the original GCALDaemon:
i. Configuration is kept in the home dir, where it belongs
(the original keeps it in /usr/local/sbin, no obvious way to move it)
ii. A script is provided to easily stop the daemon, not provided in the original.