[ports-i386@FreeBSD.org: gtk-2.8.11 failed on i386 6]
Joe Marcus Clarke
marcus at marcuscom.com
Thu Feb 2 11:25:11 PST 2006
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Dejan Lesjak wrote:
> On Thursday 02 February 2006 18:35, 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.
>
> Oh. The thing is that it's easy to check if encodings/large/fonts.cache-1 is
> empty and remove it in that case. On the other hand encodings/fonts.cache-1
> contains the line pointing to "large" subdir so I was thinking of first
> removing encodings/large/fonts.cache-1 if it is empty, then encodings/large
> directory, then running fc-cache on encodings and remove
> encodings/fonts.cache-1 if it's empty. If fc-config is not present some
> parsing will be necessary...
> Is there a way fc-cache could ignore encodings subdirectory?
>
>> The strange thing is that fontconfig removes all
>> fonts.cache-1 files under /usr/X11R6/lib/X11/fonts upon deinstallation.
>
> Perhaps generating and removing cache files should be made responsibility of
> fonts ports? IIRC quite some of them handle it already. That could also avoid
> running fc-cache with default settings thus avoiding fonts.cache-1 files
> under encodings.
This is doable. I could remove the cache generation and cleaning code
from fontconfig once all font ports have been updated to run fc-cache
themselves. This would require all font ports to depend on fontconfig,
though.
Joe
- --
PGP Key : http://www.marcuscom.com/pgp.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFD4lyHb2iPiv4Uz4cRAvuJAJ45lEpJLzWMgx299GEGAp3lHDRFnQCfQJqM
yrAmIfG80bdkriXXqxp9Apc=
=rKpx
-----END PGP SIGNATURE-----
More information about the freebsd-gnome
mailing list