Subject: bug#18085: closed (Re: bug#18085: libc locales moved to separate package)

From: [email-masked] (GNU bug Tracking System)
Date: Mon, 20 Apr 2015 13:37:04 +0000

Your bug report

#18085: libc locales moved to separate package

which was filed against the guix package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to [email-masked].

-- 
18085: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=18085
GNU Bug Tracking System
Contact [email-masked] with problems

Subject: Re: bug#18085: libc locales moved to separate package
From: [email-masked] (Ludovic Courtès)
To: [email-masked]
Date: Mon, 20 Apr 2015 15:36:16 +0200
List-Id: <debbugs-submit.debbugs.gnu.org>

[email-masked] (Ludovic Courtès) skribis:

> The ‘locales’ output of libc is huge, and contains way more locale data
> than anyone needs.

This was done in Nov. 2014, commit 97e1120.

Ludo’.

Subject: libc locales moved to separate package
From: [email-masked] (Ludovic Courtès)
To: [email-masked]
Date: Tue, 22 Jul 2014 23:45:47 +0200
List-Id: <debbugs-submit.debbugs.gnu.org>

The ‘locales’ output of libc is huge, and contains way more locale data
than anyone needs.

We should follow roughly what other distros do, that is:

  • Provide just 1 or 2 locales by default, in the ‘locales’ output (say
    en_US.utf8 and en_US.iso88591).

  • Add a parametric package that builds the specified locales, which
    users can choose to install and add to their $LOCPATH.

The big ‘locale-archive’ will actually be ignored when $LOCPATH is set,
as per locale/findlocale.c:

  /* We really have to load some data.  First we try the archive,
     but only if there was no LOCPATH environment variable specified.  */
  if (__glibc_likely (locale_path == NULL))
    {
      struct __locale_data *data
	= _nl_load_locale_from_archive (category, name);

Ludo’.