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