Hi,
> > > Why it needs another config file?
> > > Is there any reason that ptex-jisfonts package can't use dvipdfmx.cfg
> > > file?
> >
> > It's a known interface provided by dvipdfmx Debian package. If you're
> > breaking it, take both parts.
>
> Is there any other package that uses the config file? If there is no reason
> that ptex-jisfonts package can't use default configuration file, it's a bug
> of ptex-jisfonts package. Please make it use default config file or report a
> bug for that package. I think we need update-dvipdfmx or something like
> that.
>
To properly fix the problem at hand, dvipdfmx should probably have a
directory where it reads all configuration sequentially from.
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.
Note that files in debian/patch seems to be unused.
[1]
$ diffstat *diff.gz
config.guess | 1465 ++++++++++++++++++++++++++
config.sub | 1569 ++++++++++++++++++++++++++++
data/config/dvipdfmx.cfg | 2
debian/80DVIPDFMx.cnf | 3
debian/changelog | 184 +++
debian/control | 22
debian/copyright | 32
debian/dirs | 5
debian/docs | 2
debian/patch/arphic.diff | 20
debian/patch/fontmappsx.diff | 10
debian/patch/libpaper.patch | 66 +
debian/patch/wrong_assumption_on_char.patch | 28
debian/postinst | 18
debian/postrm | 13
debian/rules | 104 +
regards,
junichi
--
[EMAIL PROTECTED],netfort.gr.jp} Debian Project
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
