Policy, updmap --enable and updmap.cfg in /etc or /var (was: Bug#269930: tetex-bin: pdflatex complains of missing fonts and uses a different (uglier) font)
(Moving from the bug address to the list, it's no longer related to the bug)
Frank Küster <frank@debian.org> wrote:
>>> > And we should abolish that update-updmap and use the mechanisms of
>>> > updmap itself. Then updmap.cfg could go back to /etc.
>>>
[...]
> Okay, I agree that we should get rid of update-updmap post sarge.
But I am not so sure that moving updmap.cfg back to /etc is a good
idea. It will often be changed by scripts, and when the tetex-packages
are upgraded and come with a new version of updmap.cfg, the user sees a
prompt (config file changed by you or a script...) and has a hard time
to handle it.
Or we don't make it a conffile, but copy it in postinst. But then we
have to check existing files (which tetex version? which additional map
files), and we cannot use ucf for this. Unless, of course, we change
updmap to use ucf. But this wouldn't be much better than using our own
binary, update-updmap - in any case we have some additional code to care
for.
Hm. Putting updmap.cfg below /var, on the other hand, could be regarded
to be a policy violation when we no longer have update-updmap. Would it
be in order to just point the user to --enable and --disable,
policy-wise?
Regards, Frank
--
Frank Küster, Biozentrum der Univ. Basel
Abt. Biophysikalische Chemie
Reply to: