Description of problem: In /usr/share/doc/rpm-4.4.2 of rpm-4.4.2-46.fc7 package, almost doc here are in LaTeX/TeX source format !!! Version-Release number of selected component (if applicable): rpm-4.4.2-46.fc7 How reproducible: Just less file and see :) Steps to Reproduce: 1. cd /usr/share/doc/rpm-4.4.2 2. less FILE 3. Actual results: Almost are LaTeX/TeX source !!! Expected results: Please ship ONLY plain text doc, no LaTeX/TeX source, no PDF, no HTML Please !!! Additional info:
It's not time for an April's fool! I have the same package installed, and it's all plain text, both by inspection as by executing the "file" command: "rpm -q rpm": rpm-4.4.2-46.fc7 BETA-GPG-KEY: PGP armored data public key block builddependencies: ASCII English text buildroot: ASCII English text CHANGES: ASCII English text conditionalbuilds: ASCII English text dependencies: ASCII English text format: ASCII English text GROUPS: ASCII text hregions: ASCII English text macros: ASCII English text multiplebuilds: ASCII English text queryformat: ASCII English text relocatable: ASCII English text rollbacks: ASCII English text RPM-GPG-KEY: ASCII English text RPM-PGP-KEY: ASCII English text signatures: ASCII English text spec: ASCII English text triggers: ASCII English text tsort: ASCII English text
Hello! The files contains some LaTex controls. For examples, "triggers" contains: /*! \page triggers Trigger scriptlets [line 1] [...] \subsection triggers_example A Simple Example [line 10] [...] \verbatim [line 23] 1) sendmail is installed 2) vmail is installed 3) sendmail is removed 4) vmail is removed \endverbatim and so on. The files are perfectly readable, though.
Yes, LaTeX/TeX sources are ... plain text too. So they are READABLE. But I think this is definitively a bug of Packager ! because LaTeX is created for compiling, NOT for reading as a document of RPM package.
The docs have some resemblance to LaTeX sources but they're nowhere near valid LaTeX. Turning them into valid LaTeX would of course be possible, but that'd reduce the plain-text readability quite a bit, and as the current set of docs are just assorted bits about this and that, forming a "real document" out of them doesn't make much sense.