On Thu, May 18, 2006 at 08:36 +0200, Frank Küster wrote: > Julian Gilbey <[EMAIL PROTECTED]> wrote: > > >> Under what circumstances are > >> the files in there executed? > > > > When paperconfig is executed. Not when the libpaper1 package is > > installed or upgraded, though (is this a bug?).
I guess we have to ask the libpaper maintainers how this is to be used properly. > Don't know. Should we call paperconfig in our postinst? IMO the script placed in /etc/paperconf.d should exit, if paperconfig is not installed. Then it should be possible to call this script during our postinst without depending on libpaper-utils. > >> 'texconfig paper $paper' configures dvipdfm and xdvi, too. So these > >> lines are unnecessary. In addition, there is a debian specific patch in > >> dvipdfm that makes it use libpaper directly. Should we remove that then? > > > > OK. Didn't realise that. > > I think if we try to configure most programs to use libpaper defaults, > it is better to do it consistently. This means dvipdfm should use this > method, too, and we can drop the patch. At least if the resulting > functionality is identical; I cannot judge this. The dvipdfm patch does two things. It increases the number of papersizes known to dvipdfm and it adds support for libpaper. I would vote for keeping the additional papersizes (maybe even propagating that part upstream) but removing the direct libpaper suppport. In addition, I would vote for only supporting "a4" and "letter" via a script in /etc/paperconf.d. This would be a regression for dvipdfm, but to me consistency is very important. cheerio ralf