public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin-xfree@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: fontconfig-2.11.1-1
Date: Tue, 13 May 2014 21:14:00 -0000 [thread overview]
Message-ID: <53728B3C.3000405@cornell.edu> (raw)
In-Reply-To: <537282B0.3090603@users.sourceforge.net>
On 5/13/2014 4:38 PM, Yaakov (Cygwin/X) wrote:
> On 2014-05-12 20:45, Ken Brown wrote:
>> On 5/9/2014 11:07 AM, Yaakov (Cygwin/X) wrote:
>>> This is an update to the latest upstream release. The Windows font
>>> directory has been removed from the default fonts path due to issues
>>> caused by stale caches; a separate package to add it to the path, as
>>> well as keep the cache current automatically, should be available soon.
>>
>> You also removed /usr/share/ghostscript/fonts,
>> /usr/share/texmf-dist/fonts/opentype,
>> /usr/share/texmf-dist/fonts/truetype, and
>> /usr/share/texmf-dist/fonts/type1. Was that intentional?
>
> Yes, because it seems that they would also have this issue because
> nothing in the providing packages updates the cache. (cygport only
> generates fontconfig postinstall scripts for /usr/share/fonts.)
I don't know about the ghostscript fonts, but cygport does generate the
appropriate fc-cache commands in the postinstall scripts for the
texlive-collection-* packages that install fonts. This is done in
__prep_texlive() in src_postinst.cygpart.
Ken
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
prev parent reply other threads:[~2014-05-13 21:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 15:15 Yaakov (Cygwin/X)
2014-05-13 1:45 ` Ken Brown
2014-05-13 20:38 ` Yaakov (Cygwin/X)
2014-05-13 21:14 ` Ken Brown [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=53728B3C.3000405@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-xfree@cygwin.com \
/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.
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).