Re: Another way to deal with the Font Map Problem
Florent Rougon <f.rougon@free.fr> wrote:
> Frank Küster <frank@debian.org> wrote:
>
> Yes...
>
>> There is one other possibility, however. We could patch the updmap
>> script (or ask Thomas for this) to run with less restrictive settings
>> upon request. This first run would then be used to check which map files
>> are not found, and then we could do a second run (either of updmap with
>> the needed --disable-map commands, or of update-updmap, omitting the
>> files which specify non-existant map files).
>
> I don't like this idea much, because if you opt for the one-run
> solution, then updmap will ignore inexistent map files, which can be
> confusing for users (a broken config silently failing is usually
> confusing). And if you opt for the two-runs solution, it means to are
> going to deactivate lines in .cfg files (theoretically, .cfg files
> should be deactivated as a whole, when the package that shipped them is
> removed, but some map files could live under /usr/local/share/texmf/,
> and updmap would find them...), but are you going to fiddle with those
> provided by users? No. Then, you would need to be able to distinguish
> them from those provided by packages...
No, not exactly. We could run (the second time) updmap with "--disable
$notfoundmap". The files in /etc/texmf/updmap.d/ would not be changed,
but /var/lib/texmf/web2c/updmap.cfg would not contain all lines that are
in *.cfg files in updmap.d.
>> The big disadvantage I see that in this case the relationship between
>> conffiles (or other files in updmap.d) and the actual map files for
>> dvips, pdftex, dvipdfm is really obscured. With the setup you proposed,
>> there will be a magic comment that could also tell users where to
>> look. When updmap's output is parsed, the only way to tell which lines
>> will end up in updmap.cfg and the actual program map files is to repeat
>> the process, or look through all TEXMF trees by hand.
>
> I don't understand this paragraph, sorry. You seem to be suggesting to
> tell something else in the magic comment, what is it exactly?
Just three or five words saying that this will be ignored under certain
circumstances:
%% #~$magic$~#
%% file will be ignored unless listed in /var/lib/tetex/fontmap...
> The
> auto-include (for user .cfg files) or include-only-if-listed-under-/var
> (for package-provided .cfg files) policy for .cfg files implied by the
> magic comment I was talking about will be documented in
> update-updmap(8).
Yes, of course. But there are users who don't read manpages unless
forced to. Or _really_ pointed to. I was intending to _really_ point
them there by a comment.
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
Reply to: