On Sun, Oct 18, 2015 at 11:51 AM, Jérémy Bobbio <[email protected]> wrote: > In the present case, the fact that apertium locale packages ships > compiled locale definition files feels like a hack. I wonder if there's > a better solution. I also wonder if compiled locale definitions works > accross different versions of the glibc or if there's potential upgrade > issues hiding here.
As far as I can tell, the apertium-*-* binary packages don't actually include any compiled locale files at all; the intent is just to make sure that setting LC_ALL=en_US.UTF-8 during the build process will work. Since build-depending on locales-all is a better way to do that, I just filed a bug for apertium-en-ca with a patch. > (I must admit that I am also puzzled at the idea that there's a source > package *per locale*, that must be a hell of a burden to update and keep > in sync.) Well, it's not exactly a package per locale. :-) Apertium is an automatic translator between human languages, and a package named "apertium-aa-bb" has data files for translating between languages whose 2-letter codes are "aa" and "bb" which therefore have nothing to do with locales (apart from the fact that most locale names include one of these language codes as well). _______________________________________________ Reproducible-builds mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
