Proposal to change -DUSE_INTEROPERABLE_VTIMEZONES default

[Patrick Ohly]

On Mon, 2016-01-25 at 18:13 -0500, Allen Winter wrote:
> We discussed this last June.
> See http://lists.infradead.org/pipermail/libical-devel/2015-June/000633.html in the mailing list archives
> 
> Wish you had been participating in the discussion at that time,
> but in any event, I don't feel comfortable changing the default behavior.
> See the related bugs caused by the timezone interoperability.

Most (?) bugs were caused by switching to expanded timezones (the
current default). The only bug fixed by switching to those was about
accuracy in local applications.

So from that perspective, using interoperable timezones as default makes
more sense.

For SyncEvolution it is already to late anyway. I've not figured out how
to provide binaries for Linux distros shipping the 2.0 version of
libical yet because of the ABI changes, and once I have a solution, I
have to assume that libical will give me unsuitable timezones and
reconfigure it at runtime.

Bye, Patrick