On 18/05/16 07:43, Michał Górny wrote: > On Wed, 18 May 2016 04:07:07 +0100 > "M. J. Everitt" <m.j.ever...@iee.org> wrote: > >> I've just been party to a discussion over in the Proxy Maintainers >> channel .. and the subject of correct ways to install documentation >> popped up. It seems to me rather quirky, that there is no middle ground >> in (for example) EAPI6 to have the default documentation installed per >> https://dev.gentoo.org/~ulm/pms/head/pms.html#x1-144003r4 , PLUS maybe >> another folder or file(s). The existing framework ONLY allows *either* >> /only/ the default documentation *or* an override through the DOCS= >> variable. >> >> My idea thus, was inspired by the simple bash DOCS+= ( ) statement, that >> would allow you to append files/folders to the installdocs list, >> assuming that DOCS was pre-populated with an existing set of files. >> Obviously the status quo is set for EAPI6 and algorithms defined, but >> wondered if it could be considered for a future update/improvement cycle?! > How is this going to work? In order to pre-populate it, you need to > know the list of files. And the list of files isn't known until > src_install(). In fact, with the current behavior it's not even known > before einstalldocs is actually called, and changing that could break > stuff. > At present the DOCS to be installed in the default function are hard-coded into the PMS in 'einstalldocs' .. not exactly very good if you decided later to change it?!
signature.asc
Description: OpenPGP digital signature
