Ship as Federated Calendar, with the application ID
computer.federated.FederatedCalendar and the executable
federated-calendar, so it can be installed and run alongside GNOME
Calendar.
The settings schema follows the application ID too, so the two don't
share settings or install the same schema. The project name sets the
executable, gettext domain and data directory; the desktop file, D-Bus
service, search provider, metainfo and icons follow the application ID.
Internal resource paths and the template file names are unchanged, to
keep merging from GNOME Calendar simple.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
With -vvv, say which check stopped people from being invited to an
event: a read-only calendar, a calendar that isn't on a Core's
Nextcloud, or an event organized by someone else.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
libical 4 changed several APIs used by GNOME Calendar:
- libical-glib now provides autoptr cleanup for ICalTime, so only
define it ourselves for older versions.
- i_cal_recurrence_get/set_by_day() were removed in favor of the
dynamically sized by-rule arrays; add local helpers on top of
i_cal_recurrence_get/set_by().
- i_cal_errno_return() was renamed to i_cal_error_icalerrno().
Also make the create-tzid event test independent of line folding,
which differs between libical versions.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
davidandClaude Opus 5.5