Consensus: Locale format may change from release to release?

[Carlos O'Donell]

On 10/24/2015 12:29 AM, Mike Frysinger wrote:
> On 13 Oct 2015 10:03, Carlos O'Donell wrote:
>> I suggest we make a "Best Practices for upgrading glibc" document that
>> starts like this:
> 
> so this direction seems to miss an edge case: static binaries.  if locale
> data is incompatible, and we abort when trying to load incompatible data,
> then static binaries cannot safely use any locale functions.

I don't think we want to abort. We want to fail with NULL/EINVAL.

We want to assure people that if you upgrade your static apps will
work but they might just fall back to C/POSIX builtin locale. Maybe
another reason to get C.UTF-8 into builtin instead of external.

c.