On 05 Aug 2015 12:22, keld@keldix.com wrote:
> On Wed, Aug 05, 2015 at 12:01:26PM +0200, keld@keldix.com wrote:
> > On Wed, Aug 05, 2015 at 05:07:48AM -0400, Mike Frysinger wrote:
> > > On 12 Jun 2015 17:05, Marko Myllynen wrote:
> > > > as discussed in the thread starting at
> > > > 
> > > > https://sourceware.org/ml/libc-alpha/2015-06/msg00098.html
> > > > 
> > > > it looks like the best options is to remove locale timezone information
> > > > from locales which currently provide it (in incomplete or incorrect
> > > > fashion) rather than to start duplicating tzdata info in glibc.
> > > 
> > > thanks, pushed now!
> > 
> > That is the wrong direction. Please revert the change.
> 
> Let me explain. We would like to make the installation process easier
> for users. That is, if we can remove one more question under the installation
> process of linux, that would be a  goal. If the timezone is fully determined
> by the choice of locale, then there is no need to ask for the timezone.

having 6 out of 300+ locales define timezone info is not something people can 
rely on.  we also don't want to duplicate data that is *actively* maintained
elsewhere (the tz lists).  plus many locales span multiple timezones.

i don't see crappy UIs as a problem glibc either can or should solve.  at the
end of the day, trying to set the timezone based on the locale isn't going to
cover everyone (even a significant number of people), especially as you move
around.  i certainly don't want it being tied to my locale.  which means UIs
are required to get this right.

if you want to bring timezone data into the locale fields, then it should be
done consistently across the board and in a maintainable manner.  until that
happens, having data in a measly 6 locales is more of a disservice imo.
-mike