Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: dvipdfm - A DVI to PDF converter https://bugzilla.redhat.com/show_bug.cgi?id=437667 ------- Additional Comments From pertusus@xxxxxxx 2008-03-16 11:53 EST ------- The base page is http://gaspra.kettering.edu/dvipdfm/ you used the dvipdfmx one... There is a security issue in dvipdft since it generates files in tmp with predictible names. In texlive dvipdfm the script comes from another place and is furthermore patched. A dot is missing at the end of %description. the doc shipped should be the dvi version or even better the pdf version. To have the dvi, you should have a BuildRequires: tex(tex) and during build do something along pushd doc tex dvipdfm popd and add %docs doc/dvipdfm.dvi To have a pdf it is less obvious since the preferred way seems to be using dvipdfm itself, but since it is not installed it is not obvious that it will succeed. You can try anyway pushd doc tex dvipdfm ../dvipdfm dvipdfm popd and verify that it builds in mock, with an updated texlive that doesn't contain the dvipdfm files that should be in dvipdfm. Last issue regards the differences between config files and corresponding map files. Differences are: D "zcat -f %i | gs -q -sPAPERSIZE=a0 -sDEVICE=pdfwrite -dCompatibilityLevel=1.2 -dUseFlateCompression=true -sOutputFile=%o - -c quit" versus (-dSAFER added in texlive): D "zcat -f %i | gs -q -sPAPERSIZE=a0 -sDEVICE=pdfwrite -dCompatibilityLevel=1.2 -dUseFlateCompression=true -dSAFER -sOutputFile=%o - -c quit" a4 in texlive -p letter +p a4 The maps are, in dvipdfm the shipped maps: f cmr.map f psbase14.map f lw35urw.map In texlive, the font map created by updmap (and another map) are used: f cm-dvipdfm-fix.map f dvipdfm.map It seems to me that the dvipdfm config file in texlive is better, but I am far from being an expert in this matter. It seems to me that the config file in texlive-texmf can be kept instead of using the one in dvipdfm. The map and enc files of dvipdfm should still be shipped, though unused in the default fedora config. A Requires: tex(tex) is also certainly missing, I don't think that dvipdfm will be ok without fonts. These fonts should be brought in by kpathsea, but I think that it is better not to count on it. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. _______________________________________________ Fedora-package-review mailing list Fedora-package-review@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-package-review