Bug 1404027 - Too much space used
Summary: Too much space used
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora Localization
Classification: Fedora
Component: Project Tracking
Version: unspecified
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: noriko
QA Contact: noriko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-12 21:39 UTC by eduardo.perezesteban
Modified: 2018-02-20 04:36 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-20 04:36:41 UTC


Attachments (Terms of Use)

Description eduardo.perezesteban 2016-12-12 21:39:35 UTC
In my Fedora 24 installation, /usr/share/locale uses more that 800MB of space, to support 656 different locales; however, I just need one of them, two at most, and I guess that is the case for most of Fedora users. That is a lot of wasted space for locales that I will never use.

I think locale files should only be installed for those regions selected by the administrator, not unconditionally for the 656 variations.

Comment 1 noriko 2018-02-17 07:22:12 UTC
Hi, I just took over this component's assignee.
First, does this issue still exist? 

If so, I see this should be better asked to anaconda developers, since localization project can't really do nothing. Would you like me to forward the but to anaconda team?
What you think?

Comment 2 eduardo.perezesteban 2018-02-17 19:16:57 UTC
Yes, I am on Fedora 27, but this is still an issue.

This do not looks like an Anaconda issue. Every package I install comes with all 687 possible locales, and that is a waste of space. For example, "gnome-calculator" installs its own "/usr/share/locale/it/LC_MESSAGES/gnome-calculator.mo" file; but I am never going to configure my system in Italian, so that file is never going to be used.

I think translations must not be part of the main package, and each translation should be installed only when the admin decides to add support for that language.

Comment 3 Piotr Drąg 2018-02-17 19:53:04 UTC
I strongly disagree. Separating translations from software has far more disadvantages than advantages. Besides, this would need to be a project-wide change, and not something we can do here.

Comment 4 noriko 2018-02-18 05:34:41 UTC
ok, thank you for confirming the issue still exists.

As Piotr confirms, this is not something we can do or help.
I would like to suggest that the issue should be brought or raised to more appropriate place where the issue can be productively discussed and resolved. 

I see no point having this issue as a bug under Project tracking component, and would like to close shortly.


Note You need to log in before you can comment on or make changes to this bug.