I don't have a clear opinion on this, yet. In my use case I totally agree with you, I don't really need all this support, just a few thing are enough for me. But I understand that for the general non english speaker, non techie use case, they expect that selecting to install their desired language once they system installs you all the possible support for that language. Could we go with the full metapackage on all general UI (anaconda, DE system settings and similars) and provide a minimal metapackage at the same time? On June 15, 2019 4:12:51 AM GMT+02:00, Sundeep Anand <suanand@xxxxxxxxxx> wrote: On Sat, Jun 15, 2019 at 3:47 AM Jason L Tibbitts III <tibbs@xxxxxxxxxxx> wrote: I noticed that my F30 installs are coming out far larger than my F29 installs (by 3GB or so) and did some digging into why. With F30 we switched away from having groups named like "korean-support" that you could install to get input methods and fonts needed to display a language and instead we have metapackages named like "langpacks-ko". These metapackages have (generally) weak dependencies on the fonts and input methods as before. But other packages have reverse weak dependencies on the langpacks, which causes far more to get pulled in than was previously installed. For example, each libreoffice langpack has a "supplements" weak reverse dependency on the base "langpacks" metapackage. All of this seems fine, but my original goal was to be able to properly display, and perhaps input, various languages. But now I get translations and help files and such as well. Not just for libreoffice, but for eclipse, glibc, all of KDE as well. And I also get autocorrection rules, spelling dictionaries, hyphenation rules, and terreract OCR recognition data as well. Some of those aren't small, and the end result is that I need to bump up the size of / quite a bit. Note that turning off install_weak_deps is not an option because for most of the langpacks, _all_ of the langpack are weak. (Some do have hard font dependencies, and I'm not sure if this inconsistency is intentional.) So it seems we lost the simple "here are our suggested Korean fonts and an input method" and instead the only thing you can say is "I want everything possible to be available in Korean". Is there any way to improve the granularity here? Perhaps by having "light" and "heavy" langpacks, or splitting them by usage (translations versus simple display of text)? Agree! We probably need more discussions (I'm quite interested to work on this). This is one of the points for https://pagure.io/flock/issue/164 For now I guess I will simply extract the list of fonts and input methods I want from the langpack specfile and stop installing the actual langpack packages. - J< devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx -- Julen Landa Alustiza <julen@xxxxxxxxx> Julen Landa Alustiza <jlanda@xxxxxxxxxxxxxxxxx> _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
