Bug#873831: [debhelper-devel] Bug#873831: debhelper: [meson] Default to a UTF8 locale?

[Jussi Pakkanen]

On Fri, Sep 1, 2017 at 12:37 AM, Steve Langasek  wrote:

> Because the transition is fraught.  C.UTF-8 is now built and always
> available as part of the libc package, but it's not built into the binary
> and making libc itself treat it as a built-in default is problematic; which
> means there's a need to configure C.UTF-8 on the system at install time as
> the default.

Seems reasonable. For this particular issue Python 3.7 will do the
ANSI -> UTF-8 coercion itself so this will only be an issue until that
lands. In the mean time the simplest solution would seem to be for
debhelper to add the necessary locale setting. This should match what
some of the packages are doing already.

Bug#873831: [debhelper-devel] Bug#873831: debhelper: [meson] Default to a UTF8 locale?

[Steve Langasek]

On Thu, Aug 31, 2017 at 10:41:18PM +0300, Jussi Pakkanen wrote:
> On Thu, Aug 31, 2017 at 5:37 PM, Jeremy Bicha  wrote:

> > I believe that meson assumes it's built using a UTF-8 locale. Is this
> > something we can have debhelper handle automatically for the meson
> > buildsystem?

> A more interesting question is why does Debian insist on using a
> default setting from 1968? Utf-8 has been around and used by default
> for 10+ years. Why is it not the default for package building by now?

Because the transition is fraught.  C.UTF-8 is now built and always
available as part of the libc package, but it's not built into the binary
and making libc itself treat it as a built-in default is problematic; which
means there's a need to configure C.UTF-8 on the system at install time as
the default.

It is the correct thing to do going forward; it's just a little unclear how
to get there cleanly.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature