From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Fonts reorganization and additions
Date: Fri, 11 Sep 2015 21:36:00 -0000 [thread overview]
Message-ID: <55F34943.8010101@cornell.edu> (raw)
In-Reply-To: <1442001550.9548.6.camel@cygwin.com>
On 9/11/2015 3:59 PM, Yaakov Selkowitz wrote:
> On Fri, 2015-09-11 at 15:12 -0400, Ken Brown wrote:
>> I was referring to the fact that for terminus-fonts we see
>
>> 2015-09-10 19:57 0 etc/X11/
>> 2015-09-10 19:57 0 etc/X11/fontpath.d/
>> 2015-09-10 19:57 0 etc/X11/fontpath.d/terminus:unscaled -> /usr/share/fonts/terminus
>>
>> whereas for xorg-x11-fonts-dpi75 we see only
>>
>> 2015-09-10 20:44 0 etc/X11/fontpath.d/xorg-x11-fonts-75dpi:unscaled:pri=20 -> /usr/share/X11/fonts/75dpi
>>
>> and similarly for the other xorg-x11-fonts-* packages.
>>
>> I interpreted this as meaning that /etc/X11/fontpath.d wouldn't get created, but
>> maybe I was wrong.
>
> Generally, the leading directories aren't required, setup should be
> creating all parent directories regardless.
>
>> In any case, it apparently didn't get created for the OP, and I had the same
>> experience. On the other hand, it gets created when I manually unpack the
>> tarball, so I don't know what's going on.
>
> If you remove your /etc/X11/fontpath.d and just (re)install
> xorg-x11-fonts-Type1, does this occur? (It shouldn't.)
No, it doesn't. So your guess below is probably correct.
> The first thing that should be checked is if the code in setup which
> allows it to unpack files with "illegal" characters in Windows also
> makes sure to create parent directories. Based on these reports my
> *guess* is it doesn't but I haven't looked yet.
Ken
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2015-09-11 21:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1441962346.9784.34.camel@cygwin.com>
2015-09-11 11:21 ` Ola Strömfors
2015-09-11 16:29 ` Ken Brown
2015-09-11 16:39 ` Yaakov Selkowitz
2015-09-11 17:50 ` Nem W Schlecht
2015-09-11 19:12 ` Ken Brown
2015-09-11 19:59 ` Yaakov Selkowitz
2015-09-11 21:36 ` Ken Brown [this message]
2015-09-12 15:36 ` Jim Reisert AD1C
2015-09-13 16:10 ` Ken Brown
2015-09-14 17:40 ` Ken Brown
2015-09-14 20:55 ` Ken Brown
2015-09-12 16:33 Fergus
2015-09-12 21:59 ` Ken Brown
2015-09-13 7:02 ` Fergus
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=55F34943.8010101@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@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).