On Thu, 23 Aug 2018 at 15:43:06 +0100, Ian Jackson wrote: > There are two reasons for the standardised paths in /usr/share/doc: > 1. So that the user can find the right documentation. > 2. So that you avoid clashes with other packagkes. > > Not moving the docs about assists 1. As does providing a link > /usr/share/doc/python3-foo -> python-foo.
It would be non-Policy-compliant for python3-foo to have a symlink /usr/share/doc/python3-foo -> python-foo unless it Depends on python-foo (= ${binary:Version}), because python3-foo is required to contain or provide a corresponding /usr/share/doc/python3-foo/copyright and .../changelog.Debian.gz. However, it would be wrong for python3-foo to depend on python-foo or vice versa, because they are libraries for different interpreters and do not really have any dependency relationship. That's why the documentation is usually split out into python-foo-doc.deb. > Alternatively, when dropping the python[2] package, move the docs but > leave a symlink the other way: > /usr/share/doc/python-foo -> python3-foo Similarly, you can't do that unless python3-foo Conflicts: python-foo, which seems like overly-aggressive deprecation :-) Symlinks *inside* the per-package documentation directory are OK though, for example /usr/share/doc/python3-foo/html -> ../python-foo/html, or perhaps more realistically /usr/share/doc/python{,3}-foo/html -> ../python-foo-doc/html, which is how this works in src:dbus-python for example. smcv