From owner-freebsd-x11@FreeBSD.ORG Thu Feb 2 20:10:34 2006 Return-Path: X-Original-To: freebsd-x11@freebsd.org Delivered-To: freebsd-x11@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4CC7116A420; Thu, 2 Feb 2006 20:10:34 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE00143D45; Thu, 2 Feb 2006 20:10:33 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id A748C1A3C1D; Thu, 2 Feb 2006 12:10:33 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 09C77521F7; Thu, 2 Feb 2006 15:10:33 -0500 (EST) Date: Thu, 2 Feb 2006 15:10:32 -0500 From: Kris Kennaway To: Dejan Lesjak Message-ID: <20060202201032.GB134@xor.obsecurity.org> References: <20060202161851.GA29539@xor.obsecurity.org> <43E25CA1.3000200@marcuscom.com> <20060202193531.GA98995@xor.obsecurity.org> <200602022103.02801.dejan.lesjak@ijs.si> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="kXdP64Ggrk/fb43R" Content-Disposition: inline In-Reply-To: <200602022103.02801.dejan.lesjak@ijs.si> User-Agent: Mutt/1.4.2.1i Cc: Joe Marcus Clarke , gnome@freebsd.org, freebsd-x11@freebsd.org, Kris Kennaway Subject: Re: [ports-i386@FreeBSD.org: gtk-2.8.11 failed on i386 6] X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Feb 2006 20:10:34 -0000 --kXdP64Ggrk/fb43R Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Feb 02, 2006 at 09:03:00PM +0100, Dejan Lesjak wrote: > On Thursday 02 February 2006 20:35, Kris Kennaway wrote: > > On Thu, Feb 02, 2006 at 02:25:21PM -0500, Joe Marcus Clarke wrote: > > > 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 direct= ory > > > >>>> 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 r= oot > > > >>>> 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 settin= gs > > > > 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 fontconfi= g, > > > though. > > > > Wouldn't it be less work to just make fontconfig @dirrmtry the > > directories it removes cache files from?=20 >=20 > That would be somewhat like > @unexec find %%X11BASE%%/lib/X11/fonts/ -type d -empty -delete >=20 > > That way you also don't have=20 > > to worry about fontcache never operating on non-port font directories > > the user may have created. >=20 > It's not that trivial: unless explicitly specifying directory to it, fc-c= ache=20 > will run on directories specified in ${X11BASE}/etc/fonts/fonts.conf (and= any=20 > included file). Among others this means all subdirectories of=20 > ${X11BASE}/lib/X11/fonts. If a user would make a directory=20 > ${X11BASE}/lib/X11/fonts/mumble, fc-cache will happily populate it with e= mpty=20 > fonts.cache-1 file. Passing responsibility to run fc-cache to fonts ports= =20 > would avoid that (at least as far as ports go; user can still run fc-cach= e=20 > without directory argument of course). OK, whatever is easiest :) Kris --kXdP64Ggrk/fb43R Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFD4mc4Wry0BWjoQKURApwFAJ9PSFSuwzAgu9bEkj0M79+yyHxq4wCfdyG2 mmvEQ0rUkhlmbf/BsXEYPUE= =SUye -----END PGP SIGNATURE----- --kXdP64Ggrk/fb43R--