From: "Huang\, Ying" <huang_ying_caritas@163.com>
To: "Alex Kost" <alezost@gmail.com>, 宋文武 <iyzsong@member.fsf.org>,
"Danny Milosavljevic" <dannym@scratchpost.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: font-gnu-unifont: Call mkfontdir for pcf output
Date: Wed, 15 Feb 2017 19:51:38 +0800 [thread overview]
Message-ID: <87zihnsmd1.fsf@163.com> (raw)
In-Reply-To: <8760kb7mfv.fsf@gmail.com> (Alex Kost's message of "Wed, 15 Feb 2017 13:55:32 +0300")
Hi, All,
Alex Kost <alezost@gmail.com> writes:
> Danny Milosavljevic (2017-02-14 18:56 +0100) wrote:
>
>> Hi,
>>
>>> One problem of this solution is that some font packages (for example,
>>> fonts-misc-misc) already have fonts.dir, to avoid conflict, it is better
>>> to remove fonts.dir in all font packages and generate fonts.dir in
>>> fonts-dir-file, I think that is good. But I don't know whether others
>>> think that is a good idea.
>>
>> If it can happen that multiple packages install to share/fonts/<xxx>
>> (certainly true for share/fonts/truetype and probably true for other
>> <format>-directories) and fonts.dir then is conflicting (and doesn't
>> ever contain all the entries of the directory), I think that your idea
>> is very good (and how it was done before is dead wrong).
>
> I completely agree; removing all "fonts.dir" and "fonts.alias" files
> from packages and regenerating them at profile time looks like a good
> idea to me.
Good to know this. I will implement it as this.
Best Regards,
Huang, Ying
prev parent reply other threads:[~2017-02-15 11:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-05 5:03 [PATCH] gnu: font-gnu-unifont: Call mkfontdir for pcf output huang_ying_caritas
2017-02-05 6:49 ` 宋文武
2017-02-05 10:33 ` Huang, Ying
2017-02-05 12:19 ` Huang, Ying
2017-02-14 17:56 ` Danny Milosavljevic
2017-02-15 10:55 ` Alex Kost
2017-02-15 11:51 ` Huang, Ying [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zihnsmd1.fsf@163.com \
--to=huang_ying_caritas@163.com \
--cc=alezost@gmail.com \
--cc=dannym@scratchpost.org \
--cc=guix-devel@gnu.org \
--cc=iyzsong@member.fsf.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.