Bug #17139

Only ship locale definitions that the user can select in the Greeter

Added by intrigeri 2019-10-09 06:49:54 . Updated 2019-10-09 08:20:08 .

Status:
Confirmed
Priority:
Normal
Assignee:
Category:
Internationalization
Target version:
Start date:
Due date:
% Done:

0%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

While reviewing Bug #17132, it occurred to me that with Feature #16095, we’ve restricted the user’s choice wrt. which locale they can login with. But we still install locales-all. Chances are that this includes a large amount of data that cannot be used anymore, so presumably we should:

  • either stop installing locales-all and instead use the infrastructure provided by the locales package to generate locale definitions for the locales we make available
  • or keep installing locales-all, but delete — via a chroot hook — the locale definitions that cannot be used

But this will increase complexity of our build system, so it would be nice to start with the cheapest possible PoC that can tell us how much this change would shrink our ISO/USB images by. And then we’ll know if it’s worth it.


Subtasks


Related issues

Related to Tails - Bug #17132: Don't ship 16-greeter hook dependency Resolved
Related to Tails - Feature #16095: Curate the list of languages in Tails Greeter Resolved 2018-11-04
Blocks Tails - Feature #16209: Core work: Foundations Team Confirmed

History

#1 Updated by intrigeri 2019-10-09 06:50:09

#2 Updated by intrigeri 2019-10-09 06:50:15

  • related to Bug #17132: Don't ship 16-greeter hook dependency added

#3 Updated by intrigeri 2019-10-09 06:50:21

  • related to Feature #16095: Curate the list of languages in Tails Greeter added

#4 Updated by intrigeri 2019-10-09 08:20:08

Oh, and we could think about the same issue wrt. Tor Browser langpacks, if they’re big enough to bother.