On Thu, Feb 02, 2006 at 12:35:47PM -0500, Joe Marcus Clarke wrote: > On Thu, 2006-02-02 at 17:43 +0100, Dejan Lesjak wrote: > > [fontconfig maintainers cced] > > > > On Thursday 02 February 2006 17:18, Kris Kennaway wrote: > > > This failure is caused by the following files left in the directory > > > after xorg-font-encodings has been removed: > > > > > > -rw-r--r-- 1 root wheel 17 Feb 1 19:53 > > > /usr/X11R6/lib/X11/fonts/encodings/fonts.cache-1 -rw-r--r-- 1 root wheel > > > 0 Feb 1 19:53 /usr/X11R6/lib/X11/fonts/encodings/large/fonts.cache-1 > > > > > > These are then removed by fontconfig, but nothing cleans up the > > > directories. What should be doing that? > > > > Interesting question. fontencodings don't create fonts.cache-1, but it will > > probably be easier and less messy if they remove them so they can also remove > > directories. Can it be assumed that fontconfig is present at the time > > fontencodings are uninstalled? > > Not necessarily. fontconfig is only a build dependency of > xorg-font-encodings. Therefore, you could remove fontconfig, and keep > encodings around. The strange thing is that fontconfig removes all > fonts.cache-1 files under /usr/X11R6/lib/X11/fonts upon deinstallation. It's the converse ordering issue: xorg-font-encodings may also be removed while fontconfig is still present because they are listed as being independent. xorg-font-encodings then tries to remove its directory while the fonts.cache-1 is still there, so it fails, and when fontconfig is later removed, it cleans up these files but leaves behind the directory. In this situation where two independent ports are both touching files inside the same directory, both of them should try to @dirrmtry it at deinstallation time, so it gets cleaned up no matter what order the ports are removed in. Kris
Attachment:
pgpa9KPG64rE2.pgp
Description: PGP signature