Comment 0 for bug 1074999

This change is desirable for two reasons:

(1) In the Nov 2012 UDS session on eliminating unnecessary startup memory/performance hits, we discussed deferring indicator-datetime's invocation of geoclue until it's actually needed, such as when datetime's menu is about to show.

(2) Several users perceive datetime's use of geoclue/geoip as a breach of privacy. (See bug #944251, http://ubuntuforums.org/showthread.php?t=2000108, http://askubuntu.com/questions/106916/how-do-i-stop-geoip-from-connecting-to-the-internet-every-time-i-boot)

Inspecting the code though, it seems that the geoclue code all boils down to setting the "geo_timezone" variable for use in update_location_menu_items(). There, we build a menuitem for the geo_timezone which is only shown if com.canonical.indicator.datetime.show-auto-detected-location is true.

So, indicator-datetime could avoid unnecessary startup overhead -- and please privacy-minded users -- by deferring use of geoclue until/unless the user enables the "In the clock's menu, show time in the auto-detected location" checkbox.