Branden Robinson wrote:
> On Fri, Apr 27, 2001 at 11:49:25AM -0400, Joey Hess wrote:
> > Well, that's bad. Ok, what in the hell are these
> > /etc/X11/fonts/*/*.alias files, and why have I never heard of them
> > before, and how is their presense/absense affecting debhelper's
> > behavior anyway?
>
> They're in the Debian Policy Manual, and have been for several months.
Fine, someone else wrote the debhelper x fonts support, so I didn't pay
much attention.
I've been looking into this bug report, and trying to figure out what is
the correct way to handle removing a font package. It seems tricky:
/usr/lib/X11/fonts/foo/fonts.{alias,scale} are automatically generated
in the postinst. If there are multiple packages with fonts in foo/, then
when one is removed, its postrm needs to run the same update-fonts-*
commands that it ran in its postinst, to clean up after itself.
But what if it is the last package to provide fonts in foo/? Or worse,
what if there are other packages still installed that provide fonts
there, but it is the last to provide scalable fonts, or alias files?
Then it seems that its postrm must handle removing the appropriare
foo/fonts.{alias,scale} files, which it can only do after analyzing what
other packages provide such files in /etc/, and determining if this package
is the last one.
And that seems awefully complex for a postinst. Do update-fonts-* handle any
of this, by any chance?
An alternative would be for a font package, when removed, to
unconditionally remove foo/fonts.{alias,scale}, and then blindly call
update-fonts-alias and update-fonts-scale. This would require that if
there are no files in /etc/ for a given font directory, those commands
don't write out a fonts.foo file for it, but just exit w/o an error.
--
see shy jo
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
