From mboxrd@z Thu Jan 1 00:00:00 1970 From: Federico Beffa Subject: Re: Lack of locales in build environment Date: Tue, 10 Feb 2015 18:36:58 +0100 Message-ID: References: <87386d3d0p.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:55461) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YLEk8-0005TO-MJ for guix-devel@gnu.org; Tue, 10 Feb 2015 12:37:01 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YLEk7-0003mn-IO for guix-devel@gnu.org; Tue, 10 Feb 2015 12:37:00 -0500 In-Reply-To: <87386d3d0p.fsf@gnu.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: =?UTF-8?Q?Ludovic_Court=C3=A8s?= Cc: Guix-devel On Tue, Feb 10, 2015 at 6:13 PM, Ludovic Court=C3=A8s wrote: > Federico Beffa skribis: > >> Guile-ncurses was fixed by adding a new phase to generate the >> "en_US.UTF-8" locale during the generation of the package, but wouldn't >> it be better to keep the "en_US.UTF-8" locale? That appears to be the >> default used by most packages. > > That=E2=80=99s an open question. The vast majority of packages is happy = with > just the C locale, and some need something more. > > So far the approach has been to fix these one by one (that=E2=80=99s 4 pa= ckages > so far) but if it happens to be frequent enough or cumbersome, we can > change that in the next core-updates to have en_US.UTF-8 available by > default. The "scipy ecosystem" documentation makes use of sphinx to build the documentation and requires an UTF-8 locale. I do not know if this is specific to scipy and friends of if it is a characteristic of sphinx (that's why I speculated that there may be more python packages in need for that). >From my point of view it would be good to include en_US.UTF-8 by default for two reasons: (i) we already are at 7 (4+3) packages requiring an UTF-8 locale and, I guess, that this number is doomed to increase in the following years. (ii) This is another small step in making maintenance easier by providing an environment setting that sometimes helps. Regards, Fede