From: kanichos@yandex.ru
To: guix-devel <guix-devel@gnu.org>
Subject: Stop generating ‘fonts-dir’ directories
Date: Thu, 02 Jan 2020 13:28:17 +0300 [thread overview]
Message-ID: <787631577960897@vla1-2bebf6b1c06e.qloud-c.yandex.net> (raw)
Hello.
Currently Guix attempts to ‘merge’ font packages which install themselves into the same file path by generating ‘…-fonts-dir’ directories with symbolic links and combined fonts.dir files.
Needless to say, it is completely broken. The X.org server has not been following symbolic links to font files for some time now for security reasons.
This is the kind of hack required currently to make X server fonts work:
XFONTDIRS="$(realpath -z ~/.guix-profile/share/fonts/X11/*/!(fonts.dir) | sed 's:[^/]*\x00:\x00:g' | sort -zu | tr '\0' ,)"
There appears to be simply no way to fix the current approach. The X server will not follow symbolic links. So there is not point in generating these font directories.
reply other threads:[~2020-01-02 10:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=787631577960897@vla1-2bebf6b1c06e.qloud-c.yandex.net \
--to=kanichos@yandex.ru \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).