> >
> > To properly fix the problem at hand, dvipdfmx should probably have a
> > directory where it reads all configuration sequentially from.
>
> I think update-dvipdfmx can do that.
Where is it?
>
> > The Debian maintainer of dvipdfmx decided to patch dvipdfmx to support
> > it. See Bug#271468.
> >
> > Looking at your diff.gz[1], it looks to me you just packaged the new
> > upstream version without any consideration for backwards compatibility
> > or Debian integration. That kind of worries me.
>
> I checked the patchs before NMU the package. But the patch was only for
> Japanese-TeX related package. If the patch make dvipdfmx read all
> configuration files from some directory, we can apply the patch because it
> can be used globally. But L10N patchs must not be applied to debian main
> package. Remember debian is not a project only for Japanese.
>
> Although the maintainer of dvipdfmx decided to apply L10N patch, I thought
> that's wrong. That's why I didn't apply the patch.
It's not a L10n patch. It's a configuration patch for extensible
framework. Currently your NMU'd dvipdfmx does not provide a extention
framework without touching dvipdfmx conffile. Which means, if I modify
its configuration, dpkg will warn you.
regards,
junichi
--
[EMAIL PROTECTED],netfort.gr.jp} Debian Project
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
