On Tue, Jun 18, 2019 at 3:07 AM Jason L Tibbitts III <tibbs@xxxxxxxxxxx> wrote:
>>>>> "JP" == Jens-Ulrik Petersen <petersen@xxxxxxxxxx> writes:
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.
Okay I see, thanks: so presumably previously you were installing language support groups.
Some time back lang supports groups also pulled in langpacks of translations though.
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.
It sounds like what you probably really want is:
`dnf install @fonts @input-methods`
That will get you the default-installed system fonts and input methods (as you would get in a standard Workstation install).
This kind of problem also becomes more relevant for Toolbox containers, etc, which are also typically minimal installs.
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.)
Currently it is only really intended for a few (one or two) langpacks-* packages to be installed.
Normally just for one's native language say. This may change as the experience evolves.
I agree that installing all langpacks-* does not make sense - it will also pull in many locales packages,
possibly duplicating locales in the glibc-all-langpacks archive.
And yes as Nicolas also said maybe we need: langpacks-ko-fonts and langpacks-ko-input-methods, etc.
This needs a little more thought and discussion I feel, but we could consider it for F31 or F32 surely.
Jens
_______________________________________________ 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
