After installing x11-drivers/nvidia-drivers-390.116 emerge shows following message: (Note: Above message is only printed the first time package is installed. Please look at /usr/share/doc/nvidia-drivers-390.116/README.gentoo for future eference) The file README.gentoo is not in /usr/share/doc/nvidia-drivers-390.116/. It is in 'html' subfolder. This is the correct path: /usr/share/doc/nvidia-drivers-390.116/html/README.gentoo Reproducible: Always
It's interesting that readme.gentoo-r1.eclass would say that: elog "installed. Please look at ${EPREFIX}/usr/share/doc/${PF}/README.gentoo*" because it does not (re-)set docinto itself so it cannot know where the file ends up.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4e4563a83bb0a3c409d4a6b8fddca189ede344b8 commit 4e4563a83bb0a3c409d4a6b8fddca189ede344b8 Author: Jeroen Roovers <jer@gentoo.org> AuthorDate: 2019-03-11 22:26:04 +0000 Commit: Jeroen Roovers <jer@gentoo.org> CommitDate: 2019-03-11 22:28:19 +0000 x11-drivers/nvidia-drivers: Call docinto after readme.gentoo_create_doc readme.gentoo-r1.eclass claims it knows where README.gentoo is stored, but it does not control docinto itself. Work around it by calling docinto for the HTML content after calling readme.gentoo_create_doc. Package-Manager: Portage-2.3.62, Repoman-2.3.12 Fixes: https://bugs.gentoo.org/680088 Signed-off-by: Jeroen Roovers <jer@gentoo.org> .../nvidia-drivers-340.107-r1.ebuild | 521 +++++++++++++++++++++ ...-r1.ebuild => nvidia-drivers-390.116-r2.ebuild} | 36 +- ...-r1.ebuild => nvidia-drivers-410.104-r2.ebuild} | 36 +- ...7-r1.ebuild => nvidia-drivers-415.27-r2.ebuild} | 36 +- ...3-r1.ebuild => nvidia-drivers-418.43-r2.ebuild} | 36 +- 5 files changed, 593 insertions(+), 72 deletions(-)