Florent Rougon <[EMAIL PROTECTED]> wrote:
> Ralf Stubner <[EMAIL PROTECTED]> wrote:
>
>> Thanks! I haven't tested it yet, but from looking at the source I have
>> one comment. I think '--enable' and '--disable' can be removed from
>> $bad_options for updmap-sys, since these are debianized via Frank's
>> debianze-updmap.
>
> Mmmm... but according to updmap-sys(1):
>
> When used with the options --edit, --setoption, --enable, --disable, or
> --syncwithtrees, updmap will first write updmap.cfg(5) and regenerate
> the map files only if this file has been changed. In Debian, updmap
> has been adapted so that these options do the "right thing": change the
> configuration snippets in updmap.d instead, call update-updmap(1) to
> regenerate updmap.cfg(5) and regenerate the map files afterwards.
> Unfortunately, they will be regenerated even if updmap.cfg(5) has not
> been changed.
>
>>From this text, I would infer that --syncwithtrees is already
> debianized. It seems the manpage is in advance!
In fact, but maybe the script can catch up. For --edit, the code in
updmap is simply
edit)
${VISUAL-${EDITOR-vi}} $cnfFile;;
I think we should replace the code with a message that we cannot guess
which file the user wants to edit, and point him to the directory (maybe
with a listing).
With the syncwithtrees option, updmap creates a sed script and then runs
sed with that script over the conffile. I think if sed does not find a
match it silently skips the command, so we could simply run the sed
command iteratively over all files we have found (with the mechanisms
already present), and then reexecute updmap.
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
