, but that /usr/share/doc/

-doc is also allowed. The justification is that the documentation is easier for users to find this way. dh_installdocs attempts to compute the name of main package by chopping the -doc off the end of the doc package name in compute_doc_main_package [1]. So, my question is, have we as a team decided that: a) We want to install documentation to /usr/share/doc/

not /usr/share/doc/

-doc b) the Python 2 package is the main package and the Python 3 package is not= ? It seems to me that when Python2 is dropped, compute_doc_main_package will no longer be able to compute the main package (because the python- packages will no longer exist) and existing python--doc packages which install to /usr/share/doc/ will be in breach of the policy. [1] https://salsa.debian.org/debian/debhelper/blob/master/lib/Debian/Debhel= per/Dh_Lib.pm Christopher On 3 March 2018 at 09:56, Scott Kitterman wrote: > Look at Debian Policy, section 12.3 Additional Documentation. The answer= is > there. > > Scott K > > On Saturday, March 03, 2018 09:25:20 AM Christopher Hoskin wrote: >> Dear Ben, >> >> Did you get an answer to this? >> >> I've just noticed a change in behavior of dh_installdocs between >> debhelper compat 10 and 11. With compat 10, documents listed in >> debian/python--doc.docs (e.g. build/html) would get installed >> to /usr/share/doc/python--doc/ but with compat 11, they get >> installed to /usr/share/doc/python-/. >> >> >From the dh_installdocs man page it appears dh_installdocs has some >> >> logic to auto-detect the main package, which can be overridden with >> the --doc-main-package option. >> >> I'd like to know if dh_installdocs' default is considered correct, or >> if I should be overriding it? >> >> Thanks. >> >> Christopher >> >> On 16 July 2017 at 05:54, Ben Finney wrote: >> > Howdy all, >> > >> > Where is the best location for library documentation of a Debian Pytho= n >> > library package? >> > >> > Debian Policy =C2=A712.3 says: >> > [=E2=80=A6] installing the documentation into the documentation di= rectory of >> > the main package is preferred since it is independent of the >> > packaging method and will be easier for users to find. >> > >> > This is clear enough where a library package =E2=80=98libfoo=E2=80=99 = is the main >> > package. The documentation package =E2=80=98libfoo-doc=E2=80=99 can in= stall the >> > documentation to =E2=80=98/usr/share/doc/libfoo/=E2=80=99. >> > >> > >> > With the split in Python runtime systems, though, there is commonly no= t >> > a single =E2=80=9Cmain package=E2=80=9D. Typically there are two, =E2= =80=98python3-foo=E2=80=99 and >> > =E2=80=98python-foo=E2=80=99. >> > >> > The documentation package =E2=80=98python-foo-doc=E2=80=99 then has no= one obvious place >> > to install the documentation: >> > >> > * Installing to =E2=80=98/usr/share/doc/python-foo-doc/=E2=80=99 is di= scouraged by the >> > >> > above Policy section. I agree that is not necessarily an obvious pla= ce >> > for a user to look for =E2=80=98python3-foo=E2=80=99 documentation. >> > >> > * Installing to =E2=80=98/usr/share/doc/python-foo/=E2=80=99 or >> > >> > =E2=80=98/usr/share/doc/python3-foo/=E2=80=99 is incorrect if the co= rresponding >> > library package is not installed. >> > >> > Compounding this is the fact we are (rightly, IMO) moving toward Pytho= n >> > 3 as the primary runtime, and discouraging new Python 2 packages. Is >> > =E2=80=98python3-foo=E2=80=99 then the =E2=80=9Cmain package=E2=80=9D = by the Policy statement above? >> > >> > A symlink could be used, from =E2=80=98/usr/share/doc/libfoo-doc=E2=80= =99 to >> > =E2=80=98/usr/share/doc/libfoo=E2=80=99. But that still runs into the = problem of *which* >> > package should be assumed. >> > >> > And if the documentation package *only* is installed, where should it >> > install its documentation and symlinks? How should this be done to all= ow >> > the library packages to later be installed without changing the >> > documentation location? >> > >> > >> > I have looked at various documentation and can't see good guidance for= a >> > =E2=80=9Cone obvious way=E2=80=9D to resolve this. >> > >> > There is varying practice among packages, and anyway just because some >> > package does it a particular way doesn't mean I should copy that witho= ut >> > knowing whether it's a good idea. >> > >> > What to do? >> > >> > -- >> > >> > \ =E2=80=9CI put contact lenses in my dog's eyes. They ha= d little | >> > >> > `\ pictures of cats on them. Then I took one out and he ran around= | >> > >> > _o__) in circles.=E2=80=9D =E2=80= =94Steven Wright | >> > Ben Finney >