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?! There are methods (Again, quite clunky) to invoke the default method, amend the variable, repeat installdocs .. and/or do additional dodoc's manually, but I would have thought it was possible to incorporate into the core functions, and keep the ebuild tidy and clean (and short!). Already been shot down in flames in the IRC channel .. but going for a second round, to see if there's anyone else similarly insane, who might agree with me?! MJE
signature.asc
Description: OpenPGP digital signature
