Tom Balzer transcribed 1.2K bytes:
> 
> ng0 writes:
> 
> > I have a problem with making decision on default fonts. What if someone
> > doesn't want gnu-freetype-ttf? It is not just only this font, you can use
> > any font and sometimes this will depend on fc-cache -fv which is mentioned
> > in the documentation.
> 
> By 'in the documentation', do you mean the documentation for how fonts
> work in guix, or libreoffice's documentation? If the latter, then yes I
> see that you could start libreoffice with a gtk theme definition
> to control the fonts, allowing for other font choices. But in the case
> where one just launched libre office, wouldn't you expect that it
> 'works' running out of just the package files? If you include no font
> that wouldn't work, which seems like sacrificing basic functionality in
> order to avoid including a font that someone might not desire.
> 
> Couldn't that argument be made for any features above bare minimum for
> any application?

No, that's something entirely different from propagating fonts.

> For instance, someone might not want a support library
> for emacs that enables viewing jpegs, but the default package supports
> this. I think that removing a feature from a package definition if you
> don't want a feature makes more sense than crippling a package with
> non-sane defaults.
> 
> Tom
> 


I think you want to read past discussions on this still open problem:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=26877
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=18640
-- 
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://krosos.org/dist/keys/
https://www.infotropique.org https://krosos.org