[Pkg-lyx-devel] Re: dvipost (hopefully) ready for Debian

[Per Olofsson]

Sven Hoexter:
> *sigh* and still so many glitches left to workaround ...

Well, there are always glitches. You never get everything right from
the start.

> Well my Tex knowledge is very low (that's why I like to put Lyx between
> me and latex) but I think it's needed to register the style file
> dvipost.sty. So with my current knowledge I think Tex is required.

I think TeX will register it when it is installed, because it is
already placed in the right directory and TeX will run texhash upon
installation. So you could probably run texhash if it is available and
otherwise do nothing. But it doesn't matter much since people will
generally have TeX installed anyway.

(I don't know very much about TeX either.)

> I had to ask on the mentors mailinglist and Frank did not recommend
> dh_installtex. (hm I would like to copy and paste the link but somehow
> I'm unable to copy and paste from from elinks with gpm *grummel*)
> 
> Reading the manpage it's talking about mapfiles and language files
> and the examples have nothing with .sty. As said above I've no clue
> about the inner workings of latex.

Sounds right.

> > * There are lintian errors. Please fix them.
> Hm with which options did you run lintian?

$ lintian --version
Lintian v1.23.21
$ lintian dvipost_1.1-1_i386.deb 
E: dvipost: description-starts-with-package-name
E: dvipost: description-too-long
E: dvipost: spelling-error-in-description prefered preferred

Some other comments about the description:

"Dvipost is used for special modes, which normally needs the support ..."

"needs" should be "need" since "modes" is plural.


"With dvipost, this features ..."

should be "these" features.

> 
> > * The package is configured two times when using debuild (which uses
> >   dpkg-buildpackage). The problem seems to be the patch target
> >   dependency. You should probably move the dependency from the
> >   config.status target to the build target (before build-stamp).
> Ah that's a little bit odd. We need to patch some things in configure
> and makefile.in so the patches have to be applied bevore the first
> configure run. Guess I've to re-read some things about dpatch.

Well, even if you move it to the build target it can run before
./configure. Just put the dependency before the config.status
dependency.

> Thanks for your detailed feedback.

Glad to help!

-- 
Pelle