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.) 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. -- Yaakov -- 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
