Proposal to change -DUSE_INTEROPERABLE_VTIMEZONES default

[Allen Winter]

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.

I'm happy to re-open the discussion.


On Wednesday, January 20, 2016 07:06:42 PM Milan Crha wrote:
> 	Hi,
> while playing a bit more with libical 2.0.0 I faced a configuration
> options:
> 
> # -DUSE_INTEROPERABLE_VTIMEZONES=[true|false]
> #  Set to use inter-operable rather than exact vtimezones.
> #  Default=false (build exact vtimezones)
> #  Notes:
> #   Change the behavior at runtime using the icaltzutil_set_exact_vtimezones_support() function.
> #   Query the behavior at runtime using the icaltzutil_get_exact_vtimezones_support() function.
> 
> which feels very handy. What surprised me is its default value, the
> 'false'.
> 
> Does it make sense to any real libical user to use timezones which are
> not interoperable?
> 
> To be honest, I cannot think of any application being so much selfish
> and use non-interoperable timezones, rather than timezones which are
> useful to be exchanged between other storages. If you find any
> application which takes care only about itself, please give me the
> link. I'd like to know it.
> 
> I mean, I propose to set the default to 'true', rather than force each
> single real client of libical to first set the value in runtime, and
> only let everyone else use what it thinks is the right thing (not
> talking that some subparts of the application, like 3rd-party plugins,
> can fight about the value, even for no good reason).
> 	Thanks and bye,
> 	Milan
> 
> _______________________________________________
> libical-devel mailing list
> libical-devel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/libical-devel