>>>>> "JP" == Jens-Ulrik Petersen <petersen@xxxxxxxxxx> writes: JP> Jason, can you explain in more details (bug report is also fine) how JP> exactly you are installing? I install a generic minimal system via kickstart (booted using the Server PXE images and using the Everything repositories) and then after the reboot, ansible runs (via ansible-pull) and installs whatever is needed for the type of system it's configured to be. JP> (Because for both Workstation/Silverblue, and Server I believe, we JP> install fonts and input methods for Korean (and other langs like JP> Japanese) by default anyway It would really surprise me if a kickstart file with nothing listed under %packages installed a Korean input method. JP> Perhaps you are installing the KDE Spin? which comes without much JP> i18n support preinstalled I believe. No spins are involved; just a plain kickstart file pointed at the full repository. JP> One can also just try `dnf -n install langpacks-ko` to check what JP> fonts (and input method) would be pulled in, and you are free to JP> remove langpacks-ko anyway. Yes, though it's simpler to me to just pull the dependencies out of the langpacks specfile as I'm doing now. Unfortunately that means I have to periodically recheck if, for example, the recommended font set for Gujarati happens to change in the future. It's not an undue burden but it was nice to be able to rely on installing @gujarati-support as was the case pre-F30. JP> I am wondering how you reached 3GB - the Noto CJK fonts we now ship JP> are not small on disk - that might be a part of the problem perhaps. Well, as I wrote previously, it's things like the Libreoffice help files and the Tesseract recognition data which get pulled in via Supplements:. These can be quite large. And some of the size difference is certainly unrelated to this issue. (I was installing a total of twelve langpacks but I should probably be installing even more.) - J< _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx