From: John Darrington <john@darrington.wattle.id.au>
To: Andreas Enge <andreas@enge.fr>
Cc: Guix-devel <guix-devel@gnu.org>, Federico Beffa <beffa@ieee.org>
Subject: Re: core-updates merged!
Date: Tue, 10 Feb 2015 19:50:37 +0100 [thread overview]
Message-ID: <20150210185036.GA4455@intra> (raw)
In-Reply-To: <20150210184648.GB30353@debian>
[-- Attachment #1: Type: text/plain, Size: 1028 bytes --]
On Tue, Feb 10, 2015 at 07:46:48PM +0100, Andreas Enge wrote:
On Tue, Feb 10, 2015 at 05:38:26PM +0100, Federico Beffa wrote:
> Guile-ncurses was fixed by adding a new phase to generate the
> "en_US.UTF-8" locale during the generation of the package
This is interesting information! If I understand things correctly, I think
a solution would be to have tons of locale-XX packages, where XX stands for
the country code, the contents of which are created by calls to localedef.
And maybe a package locales-all for people who have space and do not wish
to choose. And a search path definition in glibc to set LOCPATH.
What do you think?
To me, it sounds like a good idea. I have never liked the debian way where the
locales are compiled at install time.
J'
--
PGP Public key ID: 1024D/2DE827B3
fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2015-02-10 18:50 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 16:38 core-updates merged! Federico Beffa
2015-02-10 17:13 ` Lack of locales in build environment Ludovic Courtès
2015-02-10 17:36 ` Federico Beffa
2015-02-10 18:02 ` John Darrington
2015-02-10 21:13 ` Ludovic Courtès
2015-02-10 21:15 ` Ludovic Courtès
2015-02-10 18:46 ` core-updates merged! Andreas Enge
2015-02-10 18:50 ` John Darrington [this message]
2015-02-10 19:38 ` Federico Beffa
-- strict thread matches above, loose matches on Subject: below --
2020-05-08 19:47 Marius Bakke
2020-05-08 20:48 ` Jack Hill
2017-08-18 21:24 'core-updates' status Marius Bakke
2017-08-21 21:07 ` Marius Bakke
2017-08-25 18:34 ` Marius Bakke
2017-08-25 19:55 ` Leo Famulari
2017-08-26 12:04 ` Ludovic Courtès
2017-08-26 13:30 ` core-updates merged! Marius Bakke
2017-08-27 16:03 ` Ludovic Courtès
2016-08-01 8:19 Core-updates Andreas Enge
2016-08-01 21:48 ` core-updates merged! Ludovic Courtès
2016-08-02 13:26 ` ng0
2016-08-02 17:32 ` Ludovic Courtès
2016-08-02 17:48 ` Leo Famulari
2016-08-02 21:28 ` Ludovic Courtès
2016-08-03 4:04 ` Leo Famulari
2016-08-03 16:42 ` Ludovic Courtès
2016-08-03 17:24 ` Leo Famulari
2016-08-03 17:56 ` Ludovic Courtès
2016-08-03 18:39 ` Leo Famulari
2016-08-03 20:01 ` Ludovic Courtès
2016-08-03 21:01 ` Leo Famulari
2016-08-03 21:27 ` Andreas Enge
2016-08-03 22:14 ` Leo Famulari
2016-08-06 14:42 ` Leo Famulari
2016-08-10 19:49 ` Leo Famulari
2016-08-13 7:15 ` Manolis Ragkousis
2016-08-09 3:07 ` Leo Famulari
2015-01-05 16:51 core-updates, wip-armhf, and 0.8.1 Ludovic Courtès
2015-01-16 12:39 ` core-updates merged! Ludovic Courtès
2014-03-18 14:26 core-updates merge soon! Ludovic Courtès
2014-03-26 15:46 ` core-updates merged! Ludovic Courtès
2014-03-26 15:55 ` Thompson, David
2014-03-26 16:14 ` Ludovic Courtès
2014-03-26 17:28 ` Thompson, David
2014-03-27 9:37 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150210185036.GA4455@intra \
--to=john@darrington.wattle.id.au \
--cc=andreas@enge.fr \
--cc=beffa@ieee.org \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).