Nicholas D Steeves <nstee...@gmail.com> writes: > The case is software that provides, for example, html docs, and that > opens these docs using the standard F1 (file bar help) interface. Such > docs should of course also be present in /usr/share/doc. As I see it, > the question is whether the files should actually exist in their > upstream location--which in Debian translates to /usr/share/foo/bar and > have these docs linked to /usr/share/doc, or whether they should be > moved to /usr/share/doc and be linked back to where the software expects > them. Option three is maintaining a patch for a Debian-specific > location, but I don't think that's the right solution.
> So, should Lintian not warn about > package-contains-documentation-outside-usr-share-doc if the package > links the assets to /usr/share/doc, or should the Lintian information > output recommend the inverse case (moving the docs to /usr/share/doc and > linking them back to where the software expects them)? If the files are used at runtime, Policy requires installing the files outside of /usr/share/doc and linking them to /usr/share/doc. See Policy 12.3, second-to-last paragraph. -- Russ Allbery (r...@debian.org) <https://www.eyrie.org/~eagle/>